Re: Bidirectional Networking
- From: "James Mills" <prologic@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 12 Dec 2008 12:02:21 +1000
Have a look at circuits.
http://trac.softcircuit.com.au/circuits/
It's a general purpose event-driven framework
with a focus on Component architectures and
has a good set of Networking Components,
specifically: circuits.lib.sockets
* TCPServer
* TCPClient
* UDPServer
* UDPClient (alias of UDPServer)
With circuits, there is no such thing as: serve_forever()
It'll try to stay out of your way as much as possible
and let you define your own main event loop which
could look like this:
from circuits import Manager
from circuits.lib.sockets import TCPServer, TCPClient
manager = Manager()
server =TCPServer(8000)
client = TCPClient()
manager += server
manager += client
....
while True:
server.poll()
client.poll()
manager.flush()
I hope this helps you! :)
cheers
James
On Fri, Dec 12, 2008 at 10:33 AM, Emanuele D'Arrigo <manu3d@xxxxxxxxx> wrote:
Hi everybody! A networking question!
I've been looking at and tinkering a little with the various
networking modules in python. The examples are pretty clear and a
module such as the SimpleXMLRPCServer is actually simple!
All the examples though are based on a client interrogating a server,
with the client initiating the connection, obtaining something and
then closing the connection. Basically the server is a reactive party:
only if the client get in touch the server respond. What if the server
wanted to notify the client of something of interest, i.e. new data
that the client should take into consideration and potentially
process?
One option would be for the client to periodically poll the server for
changes. Fair enough, that would work. But it'd be a bit of a waste if
the changes aren't particularly frequent.
Is it possible then to establish both a server and a client in the
same application? I guess it must be possible but the examples all
rely on some kind of server loop (i.e. SocketServer.serve_forever)
that if started on both client and server sides would create two
listening parties but no talking at all! Furthermore, other libraries
might have their own loop, i.e. a graphical client has a loop to
redraw the screen and the two loops would somehow have to be
interleaved.
I'm not quite seeing how this can be done other than we threads. Is
that the way to do it? Place the listening loop in a thread while the
rest of the application does its own thing?
Or is it SocketServer.handle_request() the key? I could call this
function periodically, but what happens if a request is made while the
application is doing something else? Are the requests queued and dealt
with one per loop?
Thanks for your help!
Manu
--
http://mail.python.org/mailman/listinfo/python-list
--
--
-- "Problems are solved by method"
.
- References:
- Bidirectional Networking
- From: Emanuele D'Arrigo
- Bidirectional Networking
- Prev by Date: Re: newbie question: if var1 == var2:
- Next by Date: Re: newbie question: if var1 == var2:
- Previous by thread: Bidirectional Networking
- Next by thread: Re: Bidirectional Networking
- Index(es):
Relevant Pages
|
