> On Jan 14, 2015, at 10:29 AM, Shazron wrote:
>
> Consider constructing a JSContext and setting up HTML5 Server Sent
> Events (in essence, push for web browsers):
The data format for these events is so brain-dead simple that it's not worth
starting up a JavaScript context just to handle them.
> On Jan 14, 2015, at 9:05 AM, Steve Mills wrote:
>
> I have an opportunity to branch out to new areas (yay!) that I've never had
> the chance to work with before, an iOS app that acts as the frontend for a
> web site, receiving and sending Facebook- or Twitter-like statuses/updates.
> The ba
Consider constructing a JSContext and setting up HTML5 Server Sent
Events (in essence, push for web browsers):
http://www.html5rocks.com/en/tutorials/eventsource/basics/
http://en.wikipedia.org/wiki/Server-sent_events
On Wed, Jan 14, 2015 at 9:05 AM, Steve Mills wrote:
> I have an opportunity to
On Jan 14, 2015, at 10:05 AM, Steve Mills wrote:
>
> Or is that done more from the client side where a timer pings the server for
> updates periodically (that sounds inefficient)?
Indeed, horribly inefficient and doesn't scale--but when they mention AJAX,
that's likely what they mean. Keeping
I have an opportunity to branch out to new areas (yay!) that I've never had the
chance to work with before, an iOS app that acts as the frontend for a web
site, receiving and sending Facebook- or Twitter-like statuses/updates. The
backend and web guys on the project have mentioned using AJAX. Di
