I agree that there's a huge opportunity for the right protocol and API,
especially in mobile and non-Internet markets, but not exclusively. What
we're left with right now is email as the only open and global
store-and-forward federated communications protocol for document
collaboration - the rest e
Well, let me put it like this for my end;
As soon as there is a open API that allows persistent, yet
selectively-shared, information and works by federated servers (without
merely sending a copy to each user like email), then I'll be making clients
using it. I'll be making 3 clients probably. A bas
I have a lot on my plate but I am looking more seriously at crowdfunding
for Wave 3.0. The only way that I see Wave taking off is with clearly
segregated and secure APIs for mobile apps that interface with
apps-independent distributed waves.
All the best,
John Blossom
email: jblos...@gmail.com
p
If it is I'll be jumping for joy, but as far as I know its still pretty
tied together.
Compiling the server without GWT is the easy bit, separating the existing
client from the sever code - or recreating enough to have your own client
seamlessly communicate I don't think is very easy. I don't even
But is the app "segregated" enough now that you can still get the
functionality that one requires for concurrent edits, etc.
All the best,
John Blossom
email: jblos...@gmail.com
phone: 203.293.8511
google+: google.com/+JohnBlossom
On Wed, Apr 30, 2014 at 1:21 AM, Yuri Z wrote:
> Yes, you don
Yes, you don't have to compile the GWT.
On Wed, Apr 30, 2014 at 5:32 AM, Jim Keener wrote:
> Is there a way to build the wave server without any of the GWT front
> end? My end goal would be to use the Wave server over a websocket with
> a custom (application-specific) front end.
>
> Jim
>
>
