David Snopek writes:
> POE::Component::Server::Stomp does use Net::Stomp, but only
> Net::Stomp::Frame and only because it seemed like it would make sense
> to users to have the same object on both the client- and server-side.
> It simply acts as a container. Porting to Net::STOMP should be easy.
Good.
> However, we use Net::Stomp much more extensively in the unit tests for
> POE::Component::MessageQueue. I don't recall the details, but there
> were a number of bugs fixed by one of our contributors (Paul Driver)
> in Net::Stomp that were required for the unit tests to work correctly.
I would like to get more information about these bugs to make sure
they are not in my code too...
> Would you mind if I forwarded this e-mail to our mailing list? This
> way another contributor might take on the task.
Fine by me.
Please note however that there is a problem with the new module name
(Net::STOMP) and that it will probably be renamed soon. The code will
stay the same, only the toplevel name will change.
Cheers,
Lionel
2010/2/17 David Snopek <dsn...@gmail.com>:
> Lionel,
>
> Thanks for the information!
>
> POE::Component::Server::Stomp does use Net::Stomp, but only
> Net::Stomp::Frame and only because it seemed like it would make sense
> to users to have the same object on both the client- and server-side.
> It simply acts as a container. Porting to Net::STOMP should be easy.
>
> However, we use Net::Stomp much more extensively in the unit tests for
> POE::Component::MessageQueue. I don't recall the details, but there
> were a number of bugs fixed by one of our contributors (Paul Driver)
> in Net::Stomp that were required for the unit tests to work correctly.
> So, the situation is a bit more delicate and may take a little more
> effort.
>
> I don't have any time right now to make these changes, but will try to
> find some soon.
>
> Would you mind if I forwarded this e-mail to our mailing list? This
> way another contributor might take on the task.
>
> Thank you,
> David Snopek.
>
> 2010/2/16 Lionel Cons <lione...@cern.ch>:
>>
>> Given the lack of response of the Net::Stomp owner last year, I wrote
>> a new STOMP module that supports the features needed in the projects
>> I'm involved in. This new module is called Net::STOMP
>> (see http://search.cpan.org/dist/Net-STOMP).
>>
>> A few days ago, Leon Brocard gave me officially the maintainership of
>> Net::Stomp. Since the API are different, my plan is to keep Net::STOMP
>> and declare Net::Stomp as obsolete. If this does not work, I will
>> release a new 1.x version of Net::Stomp with my code in.
>>
>> It seems that POE::Component::Server::Stomp does use Net::Stomp. If
>> this is indeed the case, we should probably discuss how to make your
>> code use the new Net::STOMP module.