Re: Which Real Time Communications Protocol

Thanks to both of you On Jan 8, 2014 11:08 AM, "Nikolas Stevenson-Molnar" wrote: > Thank you, that's a very good point! I'm so used to thinking about > Django in the context of the request/response cycle that I didn't think > about pairing it with a websocket framework to

Re: Which Real Time Communications Protocol

Thank you, that's a very good point! I'm so used to thinking about Django in the context of the request/response cycle that I didn't think about pairing it with a websocket framework to take on that task. _Nik On 1/8/2014 3:56 AM, Tom Evans wrote: > On Mon, Dec 30, 2013 at 7:14 PM, Nikolas

Re: Which Real Time Communications Protocol

On Mon, Dec 30, 2013 at 7:14 PM, Nikolas Stevenson-Molnar wrote: > The reason for this (someone please correct me if I'm wrong on this) is that > Django isn't meant to hold connections indefinitely. Ideally you want to get > a request and turn around a response as quick as

Re: Which Real Time Communications Protocol

Thanks! Dtb/Gby === Mario R. Osorio "If I had asked people what they wanted, they would have said faster horses." -- Henry Ford http://www.google.com/profiles/nimbiotics On Fri, Dec 20, 2013 at 12:49 PM, Bill Freeman wrote: > WebSockets runs over standard HTTP or

Re: Which Real Time Communications Protocol

I would suggest using another framework or tool for this specific purpose. For example, I use the nginx-push-stream-module (https://github.com/wandenberg/nginx-push-stream-module) and have been happy with it. It's very lightweight, easy to use, and supports WebSockets and Long Polling. When I have

Re: Which Real Time Communications Protocol

I'm not aware of one, but I haven't been doing much Django lately. I guess nobody else reading this thread knows of one either. There may be a problem making websockets be passed through by (the current implementations of) mod_wsgi, Apache httpd, nginx, etc. I'm using it with Tornado (which

Re: Which Real Time Communications Protocol

On Fri, 20 Dec 2013 08:58:39 -0800 (PST) Mario Osorio wrote: > My app will have to communicate different customers (Linux devices, Windoze > devices, iOS devices and Android devices at least). > > Overall, any of these customer devices will start one of many processes and

Re: Which Real Time Communications Protocol

Thanks to everyone contributing to my question ... I will be evaluating all options soon! -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: Which Real Time Communications Protocol

Id pick Json over xml too as it's easier to manipulate and debug Json serializable python objects. You can also write your own encoders/decoders, might help: http://pymotw.com/2/json/ On Dec 21, 2013 8:01 AM, "Liam Thompson" wrote: > you could try http://json-rpc.org/ > > On

Re: Which Real Time Communications Protocol

you could try http://json-rpc.org/ On Friday, 20 December 2013 18:58:39 UTC+2, Mario Osorio wrote: > > My app will have to communicate different customers (Linux devices, > Windoze devices, iOS devices and Android devices at least). > > Overall, any of these customer devices will start one of

Re: Which Real Time Communications Protocol

Hi Bill, Is there any django project support websocket? Thanks. Regards, Dig On Dec 21, 2013 1:50 AM, "Bill Freeman" wrote: > WebSockets runs over standard HTTP or HTTPS connections, getting past > firewalls and other restrictions (e.g.; the hotel WiFi will let you web >

Re: Which Real Time Communications Protocol

Hi Serge, May I know the capacity of your system with telnet/xmlrpc? I'm intresting in this topic, and the next project could have a push scenario. Thanks. Regards, Dig On Dec 21, 2013 1:01 AM, "Sergiy Khohlov" wrote: > telnet and xmlrpc is a good choice. I'm working

Re: Which Real Time Communications Protocol

WebSockets runs over standard HTTP or HTTPS connections, getting past firewalls and other restrictions (e.g.; the hotel WiFi will let you web browse, but not use other ports). Since WebSockets is standard HTML5, libraries for it will become more and more common. There are also older "push"

Re: Which Real Time Communications Protocol

Thanks a lot Serge! Dtb/Gby === Mario R. Osorio "If I had asked people what they wanted, they would have said faster horses." -- Henry Ford http://www.google.com/profiles/nimbiotics On Fri, Dec 20, 2013 at 12:01 PM, Sergiy Khohlov wrote: > telnet and xmlrpc is a

Re: Which Real Time Communications Protocol

telnet and xmlrpc is a good choice. I'm working on the similar project Many thanks, Serge +380 636150445 skype: skhohlov On Fri, Dec 20, 2013 at 6:58 PM, Mario Osorio wrote: > My app will have to communicate different customers (Linux devices, Windoze > devices, iOS

Which Real Time Communications Protocol

My app will have to communicate different customers (Linux devices, Windoze devices, iOS devices and Android devices at least). Overall, any of these customer devices will start one of many processes and some of the other devices are required to respond by letting their users know about the