does postal support IPC in node?

[mark-hahn]

does postal support IPC in node?

[ifandelse]

@mark-hahn Great question. In the past I've had some prototype implementations to federate postal between processes in node and also client/server, but each required an underlying transport - sockets, redis, rabbitMQ, or something lower level, etc. I wish I had something ready for you in that dept, though it wouldn't be hard to manually set that sort of configuration up. When I've needed to manually bridge across boundaries, I've often set up wire taps (see also this) - filtering to the specific channel and/or topics I want to forward over the transport, and just push the full envelope as the payload. The listener on the other end (socket.io connection, for example) simply re-publishes the envelope via postal.publish, etc.

I do plan to take my earlier ideas and create plugins for postal to allow for this sort of thing in the future, though that doesn't help at the moment. You are correct, though, postal.xframe can be used to federate postal between windows in the client (and also web workers). The API may get some TLC over the coming months (since I loathe deep namespaces....starts to feel like Java or C#), but it's been pretty solid for me thus far.

[mark-hahn]

Thanks for the info.

On Tue, Aug 6, 2013 at 8:45 PM, Jim Cowart [email protected] wrote:

@mark-hahn https://github.com/mark-hahn Great question. In the past
I've had some prototype implementations to federate postal between
processes in node and also client/server, but each required an underlying
transport - sockets, redis, rabbitMQ, or something lower level, etc. I wish
I had something ready for you in that dept, though it wouldn't be hard to
manually set that sort of configuration up. When I've needed to manually
bridge across boundaries, I've often set up wire tapshttps://github.com/postaljs/postal.js/wiki/postal.addWireTap(see also
this https://github.com/postaljs/postal.diagnostics) - filtering to the
specific channel and/or topics I want to forward over the transport, and
just push the full envelope as the payload. The listener on the other end (
socket.io connection, for example) simply re-publishes the envelope via
postal.publish, etc.

I do plan to take my earlier ideas and create plugins for postal to
allow for this sort of thing in the future, though that doesn't help at the
moment. You are correct, though, postal.xframehttps://github.com/postaljs/postal.xframecan be used to federate postal between windows in the client (and also web
workers). The API may get some TLC over the coming months (since I loathe
deep namespaces....starts to feel like Java or C#), but it's been pretty
solid for me thus far.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/40#issuecomment-22227983
.