Re: Non-blocking SOAP::Lite access

Alejandro Imass <[email protected]>
Newsgroups gmane.comp.lang.perl.poe
Message-ID <1210083886.3689.9.camel@localhost>
HI,

If you are looking to implement asynchronous non-blocking outbound web
services take a look at POE::Component::Server::AsyncEndpoint

Each endpoint will run a separate process so it does no affect other
services. Yo cal pull stuff via SOAP on one side and publish it on a
STOMP queue. Then on the other side (or other system) you can subscribe
to the STOMP queue and push the info via another WebService.

Take a look at the POD which is pretty extensive and the slides
available at 

http://p2ee.org/docs/PoCo-Server-AsyncEndpoint%20-%20English.odp

The AsyncEndpoint is still a little quirky but it is working in a
production environment. There is still a long way to go but please let
me know if you are interested so I will hurry the next release which
will include a number of small fixes.




El lun, 05-05-2008 a las 12:40 -0500, P Dobranski escribió:
> I have a need for access to a web service via SOAP from within a POE-based
> program.
> I would like that access to be non-blocking, which leads me to think that
> the SOAP::Lite service object needs to
> be implemented from within a POE::Wheel::Run.
> 
> I've looked through CPAN and didn't really see an out of the box module for
> such non-blocking SOAP requests
> (I'm the SOAP client, not the server).
> 
> Are there any more efficient means to accomplish my goal or is
> POE::Wheel::Run the right path to follow?
> Thanks for any input you might have.
> 
> dobranski.cr <at> gmail dotcom
signature.asc (application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIIGousbQbaqq693oRAlKrAJ0cIDv0+VmttnpMcQH/oE6G6VdWewCfdf6j
teWdhJpV+mYT9iY6yUbTsTQ=
=pT1U
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.