Skip Menu |

This queue is for tickets about the POE-Component-Client-HTTP CPAN distribution.

Report information
The Basics
Id: 70313
Status: rejected
Priority: 0/
Queue: POE-Component-Client-HTTP
People
Owner: Nobody in particular
Requestors: RJH [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Wed Aug 17 06:23:54 2011 RJH [...] cpan.org - Ticket created
Subject: Disabling keepalive?
As POE::Component::Client::HTTP has a 'ConnectionManager', we should be able to pass an arbitrary connection manager - not just a Client::Keepalive object. Is there a suitable object I could pass that would disable keepalive entirely? For now, I'm doing: ConnectionManager => POE::Component::Client::Keepalive->new( keep_alive => 0.001, ), which seems to work (as keep_alive must be non-zero). Is there a less hacky way to do this?
  Tue Mar 06 22:52:50 2012 RCAPUTO [...] cpan.org - Correspondence added
There's currently no less hacky way to do it. I'm leaving the ticket open for now because there ought to be one. It just needs to be thought of and written. :)
  Tue Mar 06 22:52:51 2012 The RT System itself - Status changed from 'new' to 'open'
  Tue Dec 18 00:50:46 2012 RCAPUTO [...] cpan.org - Correspondence added
Someone who needs the functionality should publish a null connection manager. All it needs to do is follow POE::Component::Client::KeepAlive's interface and open completely new sockets upon request. The work-around to neuter POE::Component::Client::KeepAlive through parameters seems to be good enough for everyone so far, so I'm rejecting this as YDNI.
  Tue Dec 18 00:50:47 2012 RCAPUTO [...] cpan.org - Status changed from 'open' to 'rejected'