[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: ( Slightly off topic ) JMS and other messaging

• To: "Naren Chawla" <naren_chawla@a...>, "ajay somani" <ajay.somani@n...>, "Maciejewski, Thomas" <Thomas.Maciejewski@l...>, "XML Dev" <xml-dev@l...>
• Subject: Re: ( Slightly off topic ) JMS and other messaging
• From: "Pavithran" <pavithran.a@a...>
• Date: Sat, 21 Sep 2002 08:48:27 +0530
• References: <AOEGLCJGIFANMEODKIBGEEBJCOAA.naren_chawla@a...>

> Folks:
>
> From a "pragmatic" perspective, fundamentally, I feel JMS and SOAP are
> designed to solve two different problems -
>
> 1. I will use JMS, if I want to exchange "messages" between applications
> with following characteristics
>
>            a. mostly asynchronous (could be synchronous, but then it
defeats
> the core advantage of messaging)
>            b. preferably within the firewall
>            c. preferably all applications are built using Java
> [there are some "non-elegant" ways to get around (a) and (b)]
>
> Also, the payload could be anything - binary object, XML, etc. Most
vendors
> have first-class support for XML messages.
>
> 2. I will use SOAP, if I am running a business application (say "travel
> reservation") and I want to expose this service/API to the external world
in
> a standardized way that "external world" could discover you, understand
your
> services (WSDL) and invoke your services. And SOAP binding with HTTP helps
> you bypass the firewall issue.

 Can u explain how SOAP+HTTP bypass the firewall issue...
 we can bind SOAP+SMTP  ..even this should bypass the firewall(i think),
 I am new to this concepts can u explain more,or where can i get more
info...

 Thanks in advance,
 Pavithran
 SONY-INDIA










>
>
>
>
>
> -----Original Message-----
> From: ajay somani [mailto:ajay.somani@n...]
> Sent: Thursday, September 19, 2002 6:32 AM
> To: Maciejewski, Thomas; XML Dev
> Subject: RE:  ( Slightly off topic ) JMS and other messaging
>
>
> We use SonicMQ (sonicsoftware.com) for XML Messaging. SonicMQ uses JMS.
>
> Ajay
>
> -----Original Message-----
> From: Maciejewski, Thomas [mailto:Thomas.Maciejewski@l...]
> Sent: Wednesday, September 18, 2002 9:27 AM
> To: XML Dev
> Subject:  ( Slightly off topic ) JMS and other messaging
>
>
> I am a big fan of messaging since it seems to hide entire
> implementations from the calling routine.  I believe this is a
> competitor to soap.
>
> Anyway. Does any one here use XML and messaging?
>
> Also there seems to be people that are scared to use messaging with the
> following criticism:
>
> 1) extra layer
> 2) slow
> 3) what if the messaging company goes out of business.
>
> for 1 I actually think it is a plus many times
>
> 2) It may slow something down but at the same time may help when trying
> to scale something since it facilitates throwing hardware at a
> bottleneck
>
> 3) I think with some careful engineering one can create a very light
> layer that hides all of the messaging implementation.  If one would need
> to swap out the messaging API then it should be just a matter of
> changing one small layer of code.
>
> For example.  Create your own message like objects and then in a layer
> translate these objects into a message.
>
> I would like to hear your thoughts on messaging ... also messaging vs.
> soap.
>
>
>
> ------------------------------------------------------------------------
> ------
> This message is intended only for the personal and confidential use of
> the designated recipient(s) named above.  If you are not the intended
> recipient of this message you are hereby notified that any review,
> dissemination, distribution or copying of this message is strictly
> prohibited.  This communication is for information purposes only and
> should not be regarded as an offer to sell or as a solicitation of an
> offer to buy any financial product, an official confirmation of any
> transaction, or as an official statement of Lehman Brothers.  Email
> transmission cannot be guaranteed to be secure or error-free.
> Therefore, we do not represent that this information is complete or
> accurate and it should not be relied upon as such.  All information is
> subject to change without notice.
>
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>

• References:
  • RE: ( Slightly off topic ) JMS and other messaging
    • From: "Naren Chawla" <naren_chawla@a...>

• Prev by Date: Re: Underwhelmed (WAS: XOM micro tutorial)
• Next by Date: DOM Level -3 + normalizeDocument API
• Previous by thread: RE: ( Slightly off topic ) JMS and other messaging
• Next by thread: Microsoft's vision of data and the role of XML in that context
• Index(es):
  • Date
  • Thread