On Wed, Jul 04, 2001 at 07:15:00AM +0200, Nicholas wrote:
> SOAP is basically an RPC mechanism using XML both as
> the payload and descriptor of the request. HTTP is
> most commonly the transport protocol, but it is
> feasible to use almost any protocol. The packages and
> toolkits availabel right now suppor the use of HTTP as
> well as SMTP and POP.
>
> I would envision a JMS based SOAP service as a
> consumer of a specidied queue. A client would package
> up a request in XML (the standard for the format of
> the request being specified by SOAP) and the server
> would receive the message, unpackage the XML request,
> invoke or pass on the request and at some point return
> a SOAP response to the sender, either by a
> pre-designated queue or by a specified response queue
> defined in the request package.
>
> Does any of this make any sense ? Anyone interested in
> making a go of an implementation ?
>
> //Nicholas
>
There is already such an animal, name TRL SOAP. TRL
stands for Tokyo Research Lab (I think IBM). Ask google
for it, it's open source. incze
PS. In fact, it was a much more conceptuous thing than
just transport SOAP messages over XML. It was a bigger
infrastructure with routers etc.
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
