Skip Menu |
 

This queue is for tickets about the IO-Socket-SSL CPAN distribution.

Report information
The Basics
Id: 28889
Status: rejected
Priority: 0/
Queue: IO-Socket-SSL

People
Owner: Nobody in particular
Requestors: bbinger123 [...] yahoo.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: another request for documenation
Date: Sat, 18 Aug 2007 13:22:45 -0700 (PDT)
To: bug-IO-Socket-SSL [...] rt.cpan.org
From: Bee Binger <bbinger123 [...] yahoo.com>
Download (untitled) / with headers
text/plain 307b
Appartently socket::io::ssl needs blocking set to 0 instead of 'no' like all other sockets at creation time.. would be nice if this was documented too. --------------------------------- Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.
Download (untitled) / with headers
text/plain 657b
On Sa. 18. Aug. 2007, 16:23:53, bbinger123@yahoo.com wrote: Show quoted text
> Appartently socket::io::ssl needs blocking set to 0 instead of 'no' > like all other sockets at creation time.. would be nice if this was > documented too.
IO::Socket::SSL is derived from IO::Socket::INET which itself is an IO::Handle. Documentation of IO::Handle states clearly: $io->blocking ( [ BOOL ] ) If called with an argument "blocking" will turn on non-blocking IO if "BOOL" is false, and turn it off if "BOOL" is true. 0 is BOOL, 1 too, 'no','false','true','yes' are not BOOL. Which IO::* documents, that it should be called with blocking('no') ?


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.