in reply to Re^3: Creating Socket Connections that are persistent across multiple page loads in a single web session
in thread Creating Socket Connections that are persistent across multiple page loads in a single web session

Thank you for being patient, but sorry, I dont get it (not my best day, obviously:)). Are you suggesting that I serialize the socket and store it as a session scalar and deserialize it back in the next pass of the same session? I doubt that you can do it with sockets.

  • Comment on Re^4: Creating Socket Connections that are persistent across multiple page loads in a single web session

Replies are listed 'Best First'.
Re^5: Creating Socket Connections that are persistent across multiple page loads in a single web session
by Corion (Patriarch) on Jan 05, 2011 at 09:49 UTC

    Yes. You cannot serialize sockets. So you need a persistent program on your server that keeps the socket open. That persistent program gives the client ("web browser") a token ("a session id", "a cookie") that associates the socket with the client. When some client connects again to your server process and presents the appropriate token, you know which connection to reuse.

[reply]
      OK! Let me give implementing this a shot. Thank you for your patience :)
[reply]

        I have done this using the POE framework. I keep a persistent connection to two tcp servers and marshal all CGI connections through them, keeping track using unique Ids and using JSON for passing the data between them. 

        use POE qw(Component::Schedule
  Filter::Reference
  Component::Server::TCP
  Component::Client::TCP
  Filter::Line
  Component::Log4perl
  Component::Daemon
  );

        [download]
[reply]
[d/l]

In Section Seekers of Perl Wisdom