#3 Support asynchronous messaging

Feature Requests
closed-rejected
nobody
Transport (26)
5
2007-10-03
2003-05-22
Byrne Reese
No

Asynchronous mode is tough... there is yet no standard
way to do it. Furthermore, because Perl is stateless it
would be a small challenge to figure out how we keep
messages correlated.

What would be interesting is to be able to support other
App Server's asynchronous protocols - .NET and BEA
both support async SOAP, but each has a slightly
different protocol.

There protocols though both follow the pattern where a
client posts a message and the server accepts the
requests and generates a correlation id and returns it to
the client. The client of course has to tell the server
where to send the response. When the response is
ready, it is sent to the designated client URL with the
correlation id, and the client is responsible for actually
doing the correlation. BEA and .NET make all this really
easy because they do that state management and
correlation for you all under the covers.

Discussion

  • Martin Kutter
    Martin Kutter
    2007-10-03

    • status: open --> closed-rejected
     
  • Martin Kutter
    Martin Kutter
    2007-10-03

    Logged In: YES
    user_id=884175
    Originator: NO

    This is beyond the scope of the SOAP protocol.