• To: "Peter V. Mikhalenko" <xml-dev@s...>
• Subject: JMS OR SOAP
• From: <lakshmi@c...>
• Date: Fri, 7 Jun 2002 13:43:46 -0600 (MDT)
• Cc: <xml-dev@l...>
• In-reply-to: <00a001c20da9$ab2ea470$0300a8c0@peter>

We are using the DOM as a repository for the state of the switch and in
order
to share the state, we need to share the dom.
We could possibly access it from a common file but the only problem with
accessing from a common
file is that the file is not going to be static, and at some point there
will be multiple editors of the file
so if there is a common file or common location it would have to manage
updates from all editors
and also manage passing changes to the multiple listeners, though maybe
that would make sense to do?
we could have a common data repository / we could have a central
repository for the DOM
that can be attached to JMS MQseries or other JMS queue implementation...

the changes will be pushed onto a queue where listeners that care about it
can get the information
and we won't have to worry about the push we always push changes..

a different transport would probably be better than corba
i think either JMS or SOAP
JMS offers a lot of control, I dunno how much SOAP offers
Any ideas/suggestions _Please

• Follow-Ups:
  • Re: JMS OR SOAP
    • From: Ronald Bourret <rpbourret@r...>

• References:
  • Re: sharing dom on Virtual machines
    • From: "Peter V. Mikhalenko" <xml-dev@s...>

• Prev by Date: Xml/xpath/xslt
• Next by Date: Evangelizing RNG
• Previous by thread: Re: sharing dom on Virtual machines
• Next by thread: Re: JMS OR SOAP
• Index(es):
  • Date
  • Thread