Is the Data API really the way to go then for a normal user login, on
a (for example) Android based client, connecting directly to a wave
server?
I hesitate a lot, because the documentation and examples all seem to
be robots, or app-engine based stuff.
The instructions here for a Java based login system (http://
code.google.com/apis/wave/wavedata/authentication.html#Java) seem
vastly more complex then the webclients code;
websocket = new WaveWebSocketClient(useSocketIO(), serverurl);
websocket.connect();
...
backend = new WebClientBackend(loggedInUser, websocket);
channel = new RemoteViewServiceMultiplexer(websocket,
loggedInUser.getAddress());
websocket.attachLegacy(backend);
if (!ClientFlags.get().enableWavePanelHarness()) {
waveView.setLegacy(backend, idGenerator);
}
The parameters passed seem more like I'd expect too. (usern...@domain
etc, rather then a secret/key/token).
Not to mention the API seems to use "setCookie", which is not
something I'd expect for a non-web-browser suitable based code :?
If I'm wrong on this and DataAPI really is the way to go despite all
this, let me know - as I'm just lost trying to find a connection
method at the moment.
Cheero,
Thomas
On Nov 8, 10:35 pm, Tad Glines <[email protected]> wrote:
> The Socket.IO stuff should also work for Android and iPhone. The JavaScript
> API is very similar to that used by the native WebSockets. Also, Socket.IO
> will use WebSockets if it's available. But it added heartbeats so that the
> connection doesn't drop due to inactivity.
>
> I'm also working on a Java client for the socketio-java server. It's needed
> because the socketio-java server, even when using WebSockets, uses a special
> message format. Jetty 7.2.0 supports the newer draft 3 specification for web
> sockets and the special SOcket.IO encoding would not be needed in that case,
> but it would require everybody to upgrade to jetty 7.2.0 and I'm not sure
> which browsers support that draft version yet.
>
> -Tad
>
>
>
>
>
>
>
> On Mon, Nov 8, 2010 at 1:28 PM, James Purser <[email protected]> wrote:
> > I think your best bet is to have a look at the Data API.
>
> > James
>
> > On Mon, Nov 8, 2010 at 12:50 PM, ThomasWrobel <[email protected]> wrote:
>
> >> Thanks, but SOCKETIO is a new thing right? As a websocket replacement
> >> for (for example) webbrowsers that dont support it.
> >> I was more interested in older connection methods (JSON etc) and if
> >> they will continue to be support...or even if support has dropped
> >> already.
>
> >> I'm developing for an Android client that use's the WFP, and looking
> >> for the most suitable way to manipulate waves on the server.
>
> >> On Nov 8, 2:20 pm, x00 <[email protected]> wrote:
> >> > it is websockets by default, set USE_SOCKETIO to true for wider use.
>
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "Wave Protocol" group.
> >> To post to this group, send email to [email protected].
> >> To unsubscribe from this group, send email to
> >> [email protected]<wave-protocol%2bunsubscr...@goog
> >> legroups.com>
> >> .
> >> For more options, visit this group at
> >>http://groups.google.com/group/wave-protocol?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Wave Protocol" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected]<wave-protocol%2bunsubscr...@goog
> > legroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/wave-protocol?hl=en.
--
You received this message because you are subscribed to the Google Groups "Wave
Protocol" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en.
