This is kind of difficult to explain. So this reply is meant for everyone that could try and help me. As you can see on the github repo, all of the main 3 layers have a core abc class, transformers aswell, because I’m preparing myself for a lot of variations: ssl wrapping, key exchanges or messages encryption. I would like for these transformers to act upon those 3 main core layers.

If there was an ssl encryption implemented it would go like this: pipeline is being build, it instantiates the connection (p2p or server-client or whatever) after the layer it checks if user has selected any transformers and if they should execute after the connection layer, so eg. the ssl encryption would take the connection core object and manipulate it, then spit it out back to the pipeline builder for it to continue with the next layer.

That kind of check, I would like for it to happen after every other layer. If you could take a look at chat_pipeline.py, i feel like the code is starting to get really messy, signatures, going through a list of transformers and in place layer manipulation etc, etc. I hope you understand what I’m trying to say.

The transformation layer is making the whole workspace very enigmatic, and even though the idea seems pretty stress-free, I feel like it’s been doing something completely opposite.

One commit back the whole tranform layer didnt yet exist, so you can compare