Kolokotronis Panagiotis

Hello @aure-olli and thank you for your response :) > If you want better performances, try creating several producers, then you can send several requests at once (but you'll loose...

I think @BFriedrichs refers to #31 .

I think it should be broken into two milestones. One short term, that is implementing the essence of the requested feature; and one long term that is following the suggested...

For the client plugins I'm currently testing zero disk interaction plugins as an anti-forensics measure so for a while at least don't spend too much time on the client plugins....

I have made a PoC plugin system for the Client that has a smaller code footprint than the one currently in use and has zero disk interaction. If everything goes...

There was nothing wrong with the previous plugin system (it had a couple of pros against the one I am developing, namely consistency with the Server plugins and persistence) it's...

Just a note here too. The Zero Disk Interaction plugin system referenced above is ready and is in the v0.4.0_rc branch. I'll try to document the plugin creation asap and...

Development towards fixing this is in [fix-deadlock branch](https://github.com/panagiks/RSPET/tree/fix-deadlock). Feel free to join me with suggestions, testing and code :)

In the current state of the branch the second point (Killing off a perpetual or extremely long execution) has been implemented. Issuing a `KeyboardInterupt` while waiting for a client response...

This branch has been abandoned and is lacking some main changes that are in 0.4.0_rc ... The good news is that an alternative solution might be available. Instead of .communicate()...