3 open PoCo::MQ issues
David Snopek
This is e-mail is part apology, part a request for help and part
consolidation of information.
Over the past several months I've been engaged in the following
activities (in roughly this order): losing my job, getting married,
moving to a new country, training for a new field I have no experience
in and searching for work. Because of that I haven't had time to
handle the, currently, 3 open issues:
(1) Implementing and testing a NOOP packet type as a potential
solution to problematic firewalls:
http://groups.google.com/group/pocomq/browse_thread/thread/e7ca0ed48fa559bb
Should be simple enough to implement but testing in practice is a
must, ie. does this actually solve the issue it aims to solve in
atleast one environment. Documentation on how to code a client to
take advantage of it would be ideal. Integration into one of the
STOMP client libraries/helpers would be an extra added plus.
(2) Tests fail on Open Solaris:
http://groups.google.com/group/pocomq/browse_thread/thread/9bcec5ba2daf46fb
I did manage to get access to an Open Solaris box several weeks ago.
I began setting up the tool chain required to run PoCo::MQ but ran out
of free time before I could finish.
(3) Failing to ACK a message crashes PoCo::MQ with Perl 5.10:
http://rt.cpan.org/Public/Bug/Display.html?id=45831
I don't have a Perl 5.10 environment setup to hack on this issue. I
also don't really have the time to setup such an environment on one of
my own boxes.
Any help would be greatly appreciated! However, even if these issues
remain unsolved for another couple months, atleast this post will
alert any newcomers to the community of the list of known issues.
Happy Hacking!
David.
--
Open Source Hacker and Language Learner
http://www.hackyourlife.org/