Hi Luther, Thanks for the pointer and suggestion. orbited looks like a clean, nifty solution that I may end up using for other parts of this project.
What I'm looking for is the web2py server side: How to best handle multiplexing multiple sockets that stay open over a duration of minutes to hours. I'm thinking that I will have to run a separate socket server application, which will communicate with web2py over HTTP if it needs to do any database lookups. Thanks, gopi. On Dec 13, 9:45 am, Luther Goh Lu Feng <[email protected]> wrote: > From the discussion > herehttp://groups.google.com/group/web2py/browse_thread/thread/f7e33ec65a... > > Someone suggested used oribited:http://orbited.org/ > > On Dec 13, 7:01 am, gopiballava <[email protected]> wrote: > > > > > Hi, > > > I'm interested in adding bidirectional messaging via sockets to a > > web2py app that I am developing. Clients will do standard web2py > > database stuff, and they will also be able to do instant messaging > > with other clients > > > What is the best way to implement this within web2py? A separate sever > > process which does web2py requests to validate user/group membership > > is the first thing that comes to mind, but I'm hoping for something > > more tightly coupled within web2py. > > > Any suggestions? > > > Thanks, > > > gopi.
