Open timriot opened 11 years ago
I know that this could probably already be handled by the plugin arch, but I thought I'd ask. ;]
It depends on how you want to do it. If we are talking about a multi-transport communication, basically, we just need to propagate what already happens internally.
Each plug will then expose its own events/hooks.
Basically you should be able, through this multiwire.generate plugin, to do http://localhost:76859/assets/dump?layerId=5&output=~/Desktop/layer5.png Same thing over TCP, and websocket.
I don't know if this is something really useful since you can do the same thing writing your own plugin. Do you have a real world example?
Kilian C.
On Saturday, February 2, 2013 at 11:17 AM, Tim Riot wrote:
I know that this could probably already be handled by the plugin arch, but I thought I'd ask. ;]
— Reply to this email directly or view it on GitHub (https://github.com/kilianc/generator/issues/99#issuecomment-13027374).
v1 - I'm thinking it would be cool to publish events for other applications to subscribe to. Client applications could discover Generator instances, which publish themselves using the name of the document they are connected to, then subscribe to those instances. From then on, the receiving app would be responsible for propagating / resolving any issues on their end. For the first version, this would be a one way, broadcast API. Two way bindings / writing of layer metadata would be for v2.