[snip background]
>>
>> 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.
>There should be no problem with UDP sockets and SocketFactory. In
>fact, t/13_udp.t uses SocketFactory, and test results from Windows
>users say it passes ok. The socketfactory.perl example in the
samples
>directory also tries UDP sockets, but it uses UNIX sockets too, and
>that kills the whole program on Windows. You could comment out the
>UNIX socket stuff, and it probably would work for you.
>I'm assuming you mean Windows, by the way.
Yes, Windows I'm afraid. I'm not talking about a windows problem;
rather its getting UDP to work when you cant connect to a port. I had hacked
around with socketfactory as you suggested and the UdpClientSession
SocketFactory didn't work - specifically the 10022 error occurred on a
connect() call in SocketFactory.pm. I have changed the code by replacing the
SocketFactory with a IO::Socket similar to udp.perl and it works fine. I was
just concerned that I was missing something basic but I dont think so now.
>10022 is "Invalid argument." in WinSock-ese, and it normally
doesn't
>try to connect() for UDP sockets. I understand, though, that
>connect() does something for UDP (sets the default sendto
address?).
>Maybe Windows doesn't support that.
I'm sure my situation is not representative so I wouldn't read
anything into it.
>-- Rocco Caputo / [EMAIL PROTECTED] / poe.perl.org /
poe.sourceforge.net
*********************************************************************************************************************
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.
*********************************************************************************************************************
