OK, lets start a framework in using python in the server side and the client
side.
(1). requirements of the server side first:
1. sending HTML, XML documents to be displayed in the browsers of the clients
and receiving for user inputs are easy in modpython, django, and etc.
2. Data received in the server side has to be stored and verified for later
accesses performed from client's requests
3. data and traffic amounts to be estimated for the server in order to
process requests in terms of numbers of clients and costs per defined operation
period, well, a slow database engine that consumes a lot CPU time in the
server really sucks!
(2). Lets check the client side, too!
In scenario 1 the client side has the browser operating only via port 80.
In scenario 2 the client side has an AP. that could be invoked in the browser,
e.g. Adobe PDF reader or Apple's quick time engine
In scenario 3 AP. can invoke the browser to a cyber page in the client side
with multiple sockets via TCPIP/UDP of various ports in the AP., e.g. skype,
msn, and etc..
Assuming that programmers can use a customized python package installed in
the AP. of the client side with other tools is allowed.
--
http://mail.python.org/mailman/listinfo/python-list
