Hi,

I'd like to do a small web application where the server should be able
to push data to notify the browsers with the shortest possible delays.

Thus I thought about long polling.

As I never used this technology I am not sure about the load such an
implementation would put on the server host and whether I could use
mod_wsgi for such an appliation


My setup / intended application.
- the web server has only port 443 (https) as incoming port
-- a max of about 100 web browsers might be connected at the same time
- server should be able to notify clients with a the very short delay
- The application would be chat like. If one web browser sends some
given data to the server some other users should have their browser
react immediately.
- apart from this the server would also contain other wsgi applications


I am new to this technology and have therefore some questions.

- I assume, that for long polling all the connections would stay alive
for all the time.

Is the memory consumption with apache / mod_wsgi for 100 simultaneous
connections a major problem or is it neglectible?

Would there be any mod_wsgi parameters, which I could to tweak for
such an application?

Would  I gain a lot by not using mod_wsgi for long polling, but other
apache modules?

Are there any other suggestions how to setup such a server in a way,
that it doesn't waste too many resources?


Thanks in advance for any ideas links, recommendations.






-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en.

Reply via email to