[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#510064: marked as done (RFP: libpoe-component-client-stomp-perl -- Perl extension for the POE Environment to communicate with the STOMP protocol)

Your message dated Fri, 12 Aug 2016 09:56:37 +0000
with message-id <E1bY9Cf-0002DQ-G3@quantz.debian.org>
and subject line closing RFP: libpoe-component-client-stomp-perl -- Perl extension for the POE Environment to communicate with the STOMP protocol
has caused the Debian Bug report #510064,
regarding RFP: libpoe-component-client-stomp-perl -- Perl extension for the POE Environment to communicate with the STOMP protocol
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
510064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510064
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Sebastien Aperghis-Tramoni <sebastien@aperghis.net>

* Package name    : libpoe-component-client-stomp-perl
  Version         : 0.07
  Upstream Author : Kevin L Esteb
* URL : http://search.cpan.org/dist/POE-Component-Client- Stomp/ 
* License         : Perl
  Programming Lang: Perl
Description : Perl extension for the POE Environment to communicate with the STOMP protocol
This module is a class used to create clients that need to access a message 
server that communicates with the STOMP protocol.
It handles the nitty-gritty details of setting up the communications channel to a message queue server. You will need to sub-class this module with your 
own for it to be useful.
An attempt to maintain that channel will be made when/if that server should happen to disappear off the network. There is nothing more unpleasent then 
having to go around to dozens of servers and restarting processes.
When messages are received, specific events are generated. Those events are based on the message type. If you are interested in those events you should override the default behaviour for those events. The default behaviour is 
to do nothing.


--
Sébastien Aperghis-Tramoni

Close the world, txEn eht nepO.

--- End Message ---
--- Begin Message --- 
RFP 510064 has no visible progress for a long time, so closing.

--- End Message ---
Reply to: