Comments wanted on new POE Project

with POE is so limited, I turn to the experts here for recommendations and other ideas you might have on our general design, specially on the POE design patterns. Many thanks in advance if you have reached this far and for any help provided. Alejandro Imass Corcaribe Tecnología C.A. Guatire

Re: Comments wanted on new POE Project

) and open protocols, namely SOAP and STOMP. Best regards, Alejandro Imass Corcaribe Tecnología C.A. Guatire, Venezuela On Sun, 2007-11-11 at 13:23 -0400, Alejandro Imass wrote: Hi all, As I have learned that POE’s documentation rewards the methodical reader, this question will reward

Making a Component

All I have to do is return a session? and that's it? use POE; use POE::Component::MyAwsomeComponent; POE::Component::MyAwsomeComponent-new(); and return a session, and that's it? perldoc POE::Component doesn't offer much more, and from the code of other components that seems to be about it.

Re: Making a Component

, some will return objects, some return Session ID's to post() to, etc. It depends on the implementation and the requirements. On Nov 16, 2007 6:39 PM, Alejandro Imass [EMAIL PROTECTED] wrote: All I have to do is return a session? and that's it? use POE; use POE::Component

PoCo mandatory shutdown events?

: http://poe.perl.org/?POE_Cookbook/Creating_Components_an_Intro To all the POE gurus here, please read the last paragraph in the posted article before some-body's house blows up because of me. Best, Alejandro Imass Corcaribe Tecnología C.A. Guatire, Venezuela signature.asc Description

RFC - Namespace dissertation for EAI Toolkit

this week so please make your comments ASAP! Alejandro Imass Corcaribe Tecnología C.A. Guatire, Venezuela signature.asc Description: This is a digitally signed message part

Re: RFC - Namespace dissertation for EAI Toolkit

instead (although I would personally prefer EIP for that matter, but then again I could get sued Hohpe Co. :) ). Any one else care to share an opinion? If no objections arise within the course of this week, we will use POE::Component::EAI as our base. Best, Alejandro Imass On lun, 2007-11-26

Re: RFC - Namespace dissertation for EAI Toolkit

Thanks for your input Matt. We have had a meeting for about an hour and agree on your comments. We will publish the Asynchronous Message Endpoint Server under the top-level EAI namespace as such: EAI::AMES Thanks to all that have participated in this discussion. Alejandro Imass On lun, 2007-11

Fiddling with session once instantiated

to this session and callback one of my extended methods, forcing me to either setup another session to handle these extensions or to call the method directly (of my derived class) which sucks because it's not event-based. Thanks, Alejandro Imass signature.asc Description: Esta parte del mensaje está

Re: Non-blocking SOAP::Lite access

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

Re: Non-blocking SOAP::Lite access

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

Re: Non-blocking SOAP::Lite access

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

PoCo::Generic suports Lowecase Methods ONLY ??? (was Non-blocking SOAP::Lite access with PoCo::Generic)

of all the problems. If it so, it is not mentioned anywhere in the documentation, but I managed to get some stuff working by using lower-case methods and underscore. FYI, and just in case, I am using es_VE_UTF-8. Best, Alejandro Imass El lun, 23-06-2008 a las 10:58 -0430, Alejandro Imass escribió

Re: PoCo::Generic suports Lowecase Methods ONLY ??? (was Non-blocking SOAP::Lite access with PoCo::Generic)

]/ ) { HERE croak qq(Can't locate object method $method via package ) .ref( $self ). qq(); } El lun, 23-06-2008 a las 12:00 -0430, Alejandro Imass escribió: Ok. I think I found the problem. It seems that PoCo::Generic will ONLY deal methods in lower case

Re: PoCo::Generic suports Lowecase Methods ONLY ??? (was Non-blocking SOAP::Lite access with PoCo::Generic)

to be checking for the same thing. My suggestion is to ONLY discard all caps methods with: unless( $method =~ /[^_A-Z]/ ){ croak ... ONLY in the AUTOLOAD sub, and get rid of the later check in the map sub. Martijn Best, Alejandro Imass signature.asc Description: Esta parte del

Re: POE application with web front end

have built Again, look at offering the HTTP service with POE itself and use something like the above. \  Thanks for any suggestions ! Best, Alejandro Imass