Hi,


Up front I wish to apologise for my lack of understanding of sockets and
socket programming. The only time I've ever read anything about them is in
the POE docs. For those of you who are offended by newbie cluelessness
please stop reading...

I am currently wishing to explore POE. My problem is that my ports have been
turned off by the sysadmin in their infinite wisdom and I could never tell
them I was looking at POE let alone knew some perl (my day job is unrelated
to programming) - but that's another story...

The only socket type POE sample or test that worked was the udp.perl sample
which relied on IO::Socket rather than a socketfactory. Everything else
would give me a SEGV or the client would report unknown error number 10022
which I presume is "you cant do sockets here laddie". After digging around
for a long while I found that the socketfactory would fall over on a
C<connect> call. What could still work was C<send> and C<recv> calls. So my
question is shouldn't it be possible for a socketfactory to work with the
udp protocol despite not being able to connect. They are "connectionless"
sockets after all.

Tony


*********************************************************************************************************************
The information in this e-mail communication together with any attachments is intended 
only for the 
person or entity to which it is addressed and may contain confidential and/or 
privileged material. 
You should only read, disclose, re-transmit, copy, distribute, act in reliance on or 
commercialise the 
information if you are authorised to do so. If you are not the intended recipient of 
this e-mail 
communication, please notify us immediately by e-mail to [EMAIL PROTECTED] or 
reply by 
e-mail direct to the sender and then destroy any electronic or paper copy of this 
message.

Any views expressed in this e-mail communication are those of the individual sender, 
unless 
otherwise specifically stated. Queensland Investment Corporation does not represent, 
warrant or 
guarantee that the integrity of this communication has been maintained or that the 
communication 
is free of errors, virus or interference.
*********************************************************************************************************************

Reply via email to