POE::Component::Client::Stomp::Utils POE::Component::Client::Stomp::Utils package contains a set of utility routines for POE clients.
Download

POE::Component::Client::Stomp::Utils Ranking & Summary

POE::Component::Client::Stomp::Utils Tags

Perl module routines STOMP Poe POE clients POE routines

POE::Component::Client::Stomp::Utils Description

POE::Component::Client::Stomp::Utils package contains a set of utility routines for POE clients. POE::Component::Client::Stomp::Utils package contains a set of utility routines for POE clients that wish to use a Message Queue server that understands the Stomp protocol.SYNOPSISThis module uses Net::Stomp::Frame to create frames for usage within POE based programs that wish to communicate to Message Queue servers. Your program could use this module in the following fashion: use POE; use POE::Component::Client::Stomp; use POE::Component::Client::Stomp::Utils; my $stomp = POE::Component::Client::Stomp::Utils->new(); my $frame = $stomp->connect({login => 'test', passcode => 'test'}); $heap->{server}->put($frame);The above examples creates a "CONNENCT" frame and sends it to the server. If the connection suceeds, the server will send back a "CONNECTION" frame. The handling of that frame is left up to your input handlers.A Stomp frame consists of the following: COMMAND12 HEADERS12 BODY00Each command may have one or more headers. Some of those headers are optional. For the most part, the parameters passed to these methods are literal translations of what the protocol needs for each of the frame commands. This was done, because the protocol is described as being in flux, with a 1.0 version being available "real soon now".So, NO ERROR checking is done. How the server will handle protocol errors is highly dependent on the servers implementation. For example, the server that I have been testing against, quietly dies. You have been warned...No serialization of data is done within these routines. You will need to decide what serialiazarion is needed and perform that serialization before calling these methods. I have found the JSON is a light, and efficent serialization method. And just about every other lanaguage has a JSON implementation readily avaiable.Some terminology issues. I am using the term "channel" to describe the communications pathway to named resources. The documentation for some of the vaious Message Queue servers, are using terms such "queue", "topic" and other nouns to describe the same thing. Requirements: · Perl

POE::Component::Client::Stomp::Utils Related Software