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

Bug#510066: marked as done (RFP: libpoe-component-generic-perl -- A POE component that provides non-blocking access to a blocking object)

Your message dated Fri, 12 Aug 2016 09:56:40 +0000
with message-id <E1bY9Ci-0002Hm-La@quantz.debian.org>
and subject line closing RFP: libpoe-component-generic-perl -- A POE component that provides non-blocking access to a blocking object
has caused the Debian Bug report #510066,
regarding RFP: libpoe-component-generic-perl -- A POE component that provides non-blocking access to a blocking object
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.)


-- 
510066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510066
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-generic-perl
  Version         : 0.1100
  Upstream Author : Philip Gwyn, David Davis and Teknikill Software
* URL             : http://search.cpan.org/dist/POE-Component-Generic/
* License         : Perl
  Programming Lang: Perl
Description : A POE component that provides non-blocking access to a blocking object 

POE::Component::Generic is a POE component that provides a non-blocking
wrapper around any object. It works by forking a child process with
POE::Wheel::Run and creating the object in the child process. Method
calls on the object are then serialised and sent to the child process
to be handled by the object there. The returned value is serialised
and sent to the parent process, where it is posted as a POE event.

Communication is done via the child's STDIN and STDOUT. This means
that all method arguments and return values must survive serialisation.
If you need to pass coderefs or other data that can't be serialised,
use "callbacks", "postbacks" or "factories".

Method calls are wrapped in eval in the child process so that errors
may be propagated back to your session.

Output to STDERR in the child, that is from your object, is shown only
if debug or verbose is set. STDOUT in the child, that is from your
object, is redirected to STDERR and will be shown in the same circomstances. 


--
Sébastien Aperghis-Tramoni

Close the world, txEn eht nepO.

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

--- End Message ---
Reply to: