Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

Re^5: share socket connections amongst multiple threads?

by BrowserUk (Patriarch)
on Jul 09, 2005 at 05:04 UTC ( #473642=note: print w/replies, xml ) Need Help??

in reply to Re^4: share socket connections amongst multiple threads?
in thread share socket connections amongst multiple threads?

When the server accept()'s a connection I add the connection id to a hash ...

What do you mean by "connection id"?

My assumption is that you mean an IO::Socket::INET handle. This is a blessed ref:

use IO::Socket::Inet;; $sock = IO::Socket::INET->new( PeerAddr => '', PeerPort => 'http(80)', Proto => 't +cp' );; print $sock;; IO::Socket::INET=GLOB(0x1a05ec0)

which, for very good reason, you cannot put into a shared hash.

Basically, the methods that are attached to a blessed object like IO::Socket::INET=GLOB(0x1a05ec0) are tied to the thread in which the object handle (a GLOB in this case) is instantiated. So, if you share that object with another thread and that other thread attempts to call a method upon it, it will try to invoke code from the other thread. That cannot work, which is why Perl stops you from trying to do that.

There are two approached to solving this problem that I am aware of:

  • The first is "tried and tested", and is the method I described above. Each thread has a Thread::Queue associated with it and when it receives a message it posts a copy to each of the other threads and they send it to the client who's thread they are handling.

    This is easier to arrange by having a "controller" thread that also has a queue and each client forwards a copy of data it receives to the contoller via it's queue and it forwards it to each of the other clients.

  • The second is a little harder to explain, and whilst it has worked for me, is not (I believe) an officially sanctioned technique. That of re-blessing the handle into each thread that needs it.

    Again, this works best if a central controller thread is given access to handles from each of the client handles and it reblesses them. The clients would then forward their messages to the controller and it would forward them (directly) to the clients via the reblessed handles. This still leaves the problem of conveying those handles from the clients to the controller. Not insurmountable, but requires some jiggery pokery.

    All in all, the queues method is probably easier.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
    "Science is about questioning the status quo. Questioning authority".
    The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.
  • Log In?

    What's my password?
    Create A New User
    Domain Nodelet?
    Node Status?
    node history
    Node Type: note [id://473642]
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others scrutinizing the Monastery: (5)
    As of 2023-03-21 14:26 GMT
    Find Nodes?
      Voting Booth?
      Which type of climate do you prefer to live in?

      Results (60 votes). Check out past polls.