Maybe it's not the best forum to ask such question, but I was thinking
about making independent applications using RSB communicate with each
other. Of course they can send messages between them using MSMQ
transport, but I was thinking about plain HTTP protocol for
communication. Why? Because it's the easiest protocol to use and
configure in various environments. Now, how would it look like on
technical side - we could have something like 'http bridge' - a
component that would take messages addressed to some http endpoint
(like 'http://my.application.com/inbox') and send them to this
endpoint using normal http post. The receiver side would accept the
message and put it to local RSB endpoint, but the sender address for
that message would also be http endpoint - a http address of the
originating application. This way we could have transport-independent
means of communication, we only would have to agree on message
serialization format. Now, I don't need such component right now, but
will have to implement some communication interface for passing
messages between two apps built on top of a message bus. What do you
think -is it useful at all, or will MSMQ do just fine?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Rhino Tools Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rhino-tools-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
