yup, i'm using it with web2py. i just RTFM (for once the google docs
are decent) and their python examples work just fine in web2py. the
javascript worked as advertized.
the one thing i had to do was map the /_ah callbacks for
connect/disconnect in app.yaml to go to web2py and in web2py routes.py
to go to my controller for handling those callbacks. (and of course
web2py DAL models rather than the GAE models in the GAE docs).
good luck!
cfh
On 5/4/12 13:46 , mrtn wrote:
Thanks howesc!
This is something I am totally not aware of, and it looks promising! Are
you using it with web2py? If so, could you elaborate a bit more on how this
thing can be integrated with web2py? Many thanks!
On Friday, May 4, 2012 10:45:43 AM UTC-4, howesc wrote:
if you desire to run on google app engine you can use the channel API:
https://developers.google.com/appengine/docs/python/channel/overview.
heck you might be able to import the JS side of it into your views and use
it not on the app engine, though i have not tried it.
i am starting to use it (not for chat but for other real-time messaging)
and it seems to be working pretty well in test.
On Wednesday, May 2, 2012 3:48:41 PM UTC-7, mrtn wrote:
So I've done some research on developing a chat app with web2py. First, I
took a look of:
http://code.google.com/p/web2py/source/browse/gluon/contrib/comet_messaging.py,
and then a related tutorial using it: http://vimeo.com/38972256 (not in
english, so I might have missed a thing or two). What I can conclude from
them is that we can make a chat application *using websockets*. However,
since websockets is not supported by all the browsers except for Chrome (at
least not by default for latest versions of other major browsers, and
certainly not by their older versions), this solution has limited practical
use.
Thanks to questions previously asked in the group, I found this:
http://greg.thehellings.com/2011/05/web2py-websockets-and-socket-io-part-iii-socket-io/,
which attempts to use Tornadio (https://github.com/MrJoes/tornadio) with
Socket.io to circumvent the problem above, so that if websockets is not
available some other fall-back option is used instead. However, this method
stops working for new versions (0.7+) of Socket.io, even with the newer
Tornadio2 (https://github.com/MrJoes/tornadio2). In fact, the author of
the original blog post above eventually decided to abandon Socket.io
approach altogether after an effort to make things work:
https://github.com/mrjoes/tornadio2/issues/17.
So, does this mean that we are running out options for implementing a
practical chat application (which is probably one of the most typical
example applications made with different web frameworks these days) using
web2py? Apart from these websockets and its remedy Socket.io, is there any
other protocol/library we can use with web2py to make this happens? Would
love to hear your suggestions!
