In the states we still can't truly rely on full time always connected stable connections. We get full time, mostly connected with a lot of interruptions if on wireless and or cable connections.
That's why to me the Websockets stuff seems fraught with potential pitfalls trying to keep a socket connection open over a 90% uptime at best. Especially when it comes to mobile phones and tablets. Wireless can be spotty even in well covered areas like Mpls and Chicago. New York and LA.
I like the idea of having an always on connection, but the flexibility of dropping offline into a tunnel and resuming when I exit the tunnel is one of the things that makes stateless programming so flexible as well.
No magic answer, but I would be careful when implementing Websockets in a real-world scenario. Make sure to thing about your worst possible client connection and program for that.
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
-----Original Message-----
date: Wed, 11 Jul 2012 21:15:29 +0100
from: Kevin Turner <kevin.turner@xxxxxxxxxxxxxxx>
subject: Re: [WEB400] Websockets on the IBMi
I am not sure that the whole point of HTTP was stateless programming :) I think the whole point originally was to deliver static HTML pages to browsers on slow unreliable connections. Stateless programming evolved from that point - the point where you could not rely on a steady, reliable and fast connection between the client and the server.
Actually, with some ISPs in the UK, you still cannot rely on a steady, reliable and fast connection.... :(
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen
Sent: 11 July 2012 21:03
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] Websockets on the IBMi
Jon,
I was thinking the very same thing when I was reading the threads :-)
Sounds interesting, but the whole point of HTTP was stateless programming originally......................
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
midrange.com
