Uy, algo offtopic, pero justo lo nombra Sebastian en su post, el tema mobile, real time, node.js, socket.io ;-)
Hay concurso en Ecuador http://www.uazuay.edu.ec/udadev/ oia, mira quien va ;-) http://msmvps.com/blogs/lopez/archive/2012/10/24/node-js-en-uda-developers-challenge-2012.aspx Con respecto al tema planteado por Sebastian, en un juego, el anio pasado, usamos Socket.io contra Node.js. pero desde celulares, usamos TCP contra node.js. Y los mensajes en tiempo real los repartimos por ambos canales: los jugadores que venian de un browser, enviaban y recibian por Socket.io. Los jugadores que venian por una aplicacion C, enviaan y recibian mensajes por TCP. y ambos grupos accedian al mismo juego. Pero me temo que no en Smalltalk ;-) On Wed, Oct 24, 2012 at 1:47 PM, Sebastian Sastre < [email protected]> wrote: > Hi guys, > > this is a converstation starter to this genuine question: > > How to deliver real-time web and mobile applications? > ...that can also smoothly work offline and online? > > I know, it’s annoyingly pretentious, but... > > (a) what else would make sense? and > (b) sounds like the world will (see examples below) > (c) what chances we have to achieve it if we don’t even aim to it? > > So do we really have an alternative? > > ...continues here: > > http://sebastianconcept.com/brandIt/how-to-deliver-realtime-web-and-mobile-applications > > I really want to hear your opinion on this > > sebastian > > o/ > > -- > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > > http://www.clubSmalltalk.org -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] http://www.clubSmalltalk.org
