Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

Re: Design decision, call backs and network data

by pg (Canon)
on Jul 25, 2004 at 16:48 UTC ( [id://377285]=note: print w/replies, xml ) Need Help??


in reply to Design decision, call backs and network data

The question is a bit vague, but sounds like sort of difficulty to deal with multiple network connections. IO::Select is almost the easiest way to deal with connections with multiple sources. Take a look at the documentation, play with it, and you may come back with more specific questions.

  • Comment on Re: Design decision, call backs and network data

Replies are listed 'Best First'.
Re^2: Design decision, call backs and network data
by BUU (Prior) on Jul 25, 2004 at 19:21 UTC
    I'm not really sure how you got that impression, as theres only one network connection. On this network connection the server sends me events and such like that happen on the server. It also sends me responses to specific commands. My problem is that when I send a command to the server, I want to do something with the response, but I don't know when the response will be sent back, as the server might send back some events before the response. The place I send the request however, is in a call back for a specific packet type, so it can't handle other event packets. My question, is how do I deal with the event packets being sent back before my request response? Ignoring them isn't an option really.
[reply]

In Section Seekers of Perl Wisdom

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?

www.com | www.net | www.org
Node Status?
node history
Node Type: note [id://377285]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? • Last hour • Other CB clients
Other Users?
Others scrutinizing the Monastery: (3)
As of 2024-04-26 07:27 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found