Fixed
Status Update
Comments
de...@google.com <de...@google.com>
ni...@gmail.com <ni...@gmail.com> #2
Specially being able to talk to our XMPP bots via GTalk like:
var ws = new WebSocket("ws://talk.google.com ")
Possibilities are endless for instant communication, social games, real-time
monitoring, etc.
var ws = new WebSocket("ws://
Possibilities are endless for instant communication, social games, real-time
monitoring, etc.
ni...@gmail.com <ni...@gmail.com> #3
I've just checked. This is still broken on Android Studio 2.2
ja...@google.com <ja...@google.com> #4
In my opinion, you should stick to ASCII. Even if this was supported it would break something else. Don't do this to yourself.
ni...@gmail.com <ni...@gmail.com> #5
any sooner will gonna get this feature available? =)
ni...@gmail.com <ni...@gmail.com> #6
It is currently not on the timeline yet, however we have acknowledge that this would be
a useful feature. If you cannot wait, here is one alternative:
http://groups.google.com/group/google-appengine-
python/browse_thread/thread/a12350c582d32ea4
a useful feature. If you cannot wait, here is one alternative:
python/browse_thread/thread/a12350c582d32ea4
yb...@google.com <yb...@google.com> #7
Just to let you know, I've implemented a tiny sample app. It's actually running in two locations:
http://hybrid.typhoonae.org
http://typhoonae-hybrid.appspot.com
da...@google.com <da...@google.com>
ni...@gmail.com <ni...@gmail.com> #8
i tried on firefox 3.5 it does not support websocket? . ur code written in python?
any demo in java?
any demo in java?
yb...@google.com <yb...@google.com> #9
@8
According to
http://wiki.whatwg.org/wiki/Implementations_in_Web_browsers#Web_Sockets
Web Sockets are only implemented in Chrome dev channel (4.0.238.0 or later), although
there are efforts to implement it in Firefox and Safari/WebKit.
According to
Web Sockets are only implemented in Chrome dev channel (4.0.238.0 or later), although
there are efforts to implement it in Firefox and Safari/WebKit.
da...@google.com <da...@google.com> #10
Una de las vías de fomentar html5 es dar las herramientas adecuadas para su desarrollo,
GAE funciona sobre jetty, y este ya tiene una implementación de un servlet para
websockets, entiendo entonces que si Google apuesta por el html5 también apuesta por
websockets, por lo que esto es algo que debería implementar en GAE.
GAE funciona sobre jetty, y este ya tiene una implementación de un servlet para
websockets, entiendo entonces que si Google apuesta por el html5 también apuesta por
websockets, por lo que esto es algo que debería implementar en GAE.
ni...@gmail.com <ni...@gmail.com> #11
I'm using Websckets already with FlightGear flightsimulator to update google maps on
Chrome.
This would be wonderful to have.
Chrome.
This would be wonderful to have.
Description
If I have:
<TextView
android:id="@+id/título"
android:layout_width="match_parent"
android:layout_height="wrap_content"
/>
then this is the generated accessor in the Binding class:
public final android.widget.TextView tTulo;
instead of
public final android.widget.TextView título;
(Using gradle android plugin 2.0.0-alpha5)