Re: Socket Handle not sending data ?

[targetsmart]

in reply to Socket Handle not sending data ?

push that created socket handle(no need to push the port number too) into an array, and iterate through that array to send data when you want to.
that text file idea won't work.
I am not sure about, whether one can persistently store a socket handle into a file and use it on the next launch of the same script. This could happen rarely and I think you have not encountered a relevant situation like this.

[evilkamikaze]

[ikegami]

For starters, please use <c>...</c> instead of <pre>...</pre>.

It looks like your object got stringified

$ perl -e'
>    sub method {}
>    my $o = bless({});
>    $o->method();  # Ok
>    $o = "$o";
>    $o->method();
> '
Can't locate object method "method" via package "main=HASH(0x814ec28)"
+ (perhaps you forgot to load "main=HASH(0x814ec28)"?) at -e line 6.

Tracing back I see you read a string from a file and expect it to magically become a socket handle. That's not gonna happen.

In fact, the handle gets closed at the end of PortConn as the last reference to it ($rethandle) goes out of scope.

The idea is fundamentally flawed. A handle is a token that represents a resource the OS has handed your process. The token is useless to any other process. If you want to store something, you need to store the connection details so you can re-establish the connection.

[evilkamikaze]

Hi, Could you please point some good design options? Also, will it work if I try to make it without threads using non-blocking socket call? so if I try to connect to a port and it is not up then instead of blocking I just skip to next port without any delay. Is this something that makes more sense than previous approach? Thanks