Peter,
I've not started coding yet, but I had the same question. The only way I
could see to do this is the following, and I'll be honest, I don't know the
OS well enough yet to know if even this would work...
Since the Socket calls are blocking, I was thinking of having a daemon
"application" running in the background. I know apps are single threaded,
but I thought I read somewhere that a background program could run. This
application would call the blocking recv(). When data arrived, it would
post an event to the main application. Sends could be handled the same way,
potentially, with a queue of messages and a post to the send thread, the
send thread would then keep calling send() until the whole message got out.
Does this make any sense?
-Brian
-----Original Message-----
From: Ford, Peter [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 09, 2000 1:59 PM
To: Palm Developer Forum
Subject: Sockets and Events
I'm in the process of building an app which connects to one of our Unix
servers using a socket. It works pretty well but there's a problem. The
client (that is, the app running on the Palm) may be waiting for an event
which could be, say, a button press. However, the server may produce a
packet at any time, and my program needs to be able to respond quickly.
Now ideally, since the whole programming model for the Palm is based around
event-driven programs, I want to be able to have an event fired when data
arrives from the socket. That way my app can handle incoming packets when
they appear. The way things are right now, all I can do is periodically
check the socket to see if anything has come in.
Does anyone know: are there any network events my program can listen for? Do
I need to hack the OS to make this work?
Pete
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palm.com/devzone/mailinglists.html
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
