Hi eyepopslikeamosquito,

There's also fileno, but those numbers are re-used. I don't have much experience with fileno, so perhaps a monk who does can say more, but I imagine that if you closely keep track of when filehandles are closed, you could still use fileno to tell different connections apart.

open my $fh1, '<', '/tmp/foo' or die $!;
open my $fh2, '<', '/tmp/bar' or die $!;
print "fh1: ", fileno($fh1), "\n";
print "fh2: ", fileno($fh2), "\n";
__END__
fh1: 3
fh2: 4
[download]

Otherwise, I agree with BrowserUk: a good way to identify network connections is by properties like remote IP + remote port.

A while back I tried out POE. Its API takes quite a bit of getting used to, but once you've got the hang of it, it works well. Since each "session" has a unique ID, keeping track of clients is easy. The Cookbook is really helpful in getting started.

Hope this helps,
-- Hauke D