Non-blocking SOAP::Lite access

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

You could also look at the current POE::Component::Server::XMLRPC
server implementation (that is growing rusty with bitrot at the
moment). It makes use of XMLRPC::Lite (in the same space as
SOAP::Lite) for ideas on how to do this non-blocking style

On Mon, May 5, 2008 at 12:40 PM, P Dobranski <dobranski.cr@gmail.com> wrote:
> 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 f
or
>  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
>



--
Nicholas R. Perez

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-As...-%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 fo
r
> 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

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-As...-%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 fo
r
> 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

Nicholas, Alejandro, thanks for the excellent suggestions.

I think between Poe::Component::Server::XMLRPC and
POE::Component::Server::AsyncEndpoint I should be able to glean enough
details to get something working with SOAP::Lite.



On Mon, May 5, 2008 at 12:40 PM, P Dobranski <dobranski.cr@gmail.com> wrote:

> 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
>

I used this book: 

Programming Web Services with Perl 
By Pavel Kulchenko,  Randy J. Ray  
 
Publisher : O'Reilly 
Pub Date : December 2002 
ISBN : 0-596-00206-8 

El mar, 06-05-2008 a las 10:39 -0500, P Dobranski escribió:
> Nicholas, Alejandro, thanks for the excellent suggestions.
> 
> I think between Poe::Component::Server::XMLRPC and
> POE::Component::Server::AsyncEndpoint I should be able to glean enough
> details to get something working with SOAP::Lite.
> 
> 
> 
> On Mon, May 5, 2008 at 12:40 PM, P Dobranski <dobranski.cr@gmail.com> wrot
e:
>  

> I think between Poe::Component::Server::XMLRPC and
> POE::Component::Server::AsyncEndpoint I should be able to glean enough
> details to get something working with SOAP::Lite.

For Webservice work you might be better off using XML::Compile.  It seems mu
ch
more logical, and takes care of all the SOAP handling.

--

Med venlig hilsen
Kaare Rasmussen, Jasonic

Jasonic                 Telefon: +45 3816 2582
Nordre Fasanvej 12
2000 Frederiksberg      Email: kaare@jasonic.dk