i have bee playing around with it and i think it has a huge amount of potential but it is still very rough around the edges.<br><br><div class="gmail_quote">On Sat, Dec 5, 2009 at 7:33 AM, Aldon Hynes <span dir="ltr"><<a href="mailto:Aldon.Hynes@orient-lodge.com">Aldon.Hynes@orient-lodge.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">So far, I know of three Open Source OpenWave servers.<br>
<br>
FedOne<br>
<a href="http://code.google.com/p/wave-protocol" target="_blank">http://code.google.com/p/wave-protocol</a><br>
<br>
This is the Google version, available under Apache License 2.0. There are a<br>
lot of us running these servers. I have one up and running that any of you<br>
are free to use. Being the standard reference server, lots of people are<br>
developing around it. It is still very primative, but has some neat stuff.<br>
Key features: It federates with other FedOne servers, including the Google<br>
Sandbox. I've successfully federated with Google Sandbox and other FedOne<br>
servers in the past, but recently have been having problems federating. The<br>
production Google Server does not yet support Federation. It also supports<br>
not only the simple console client that comes with it, but QWaveClient, a<br>
nice little client written in QT. I've used the QWaveClient to connect to<br>
my server. The other thing that I find most annoying about FedOne is that<br>
currently waves are not persistent between server sessions.<br>
<br>
Ruby on Sails<br>
<a href="http://github.com/danopia/ruby-on-sails" target="_blank">http://github.com/danopia/ruby-on-sails</a><br>
This is written by a young man named Dan. I don't think he's thought much<br>
about the licensing issues. I've run this on my server, although I don't<br>
usually have it running. It looks really nice. I'm told that it now<br>
supports Federation with FedOne servers, but I haven't tested it yet. There<br>
is not a standard client/server protocol defined yet, but the folks working<br>
on FedOne appear to be evolving one and the Dan at Ruby on Sails is working<br>
on getting his code to with the emerging client server protocol. I hope and<br>
expect to be able to use a Ruby on Sails Client with a FedOne server soon,<br>
as well as using a QWaveClient or the FedOne Console Client to connect to<br>
Ruby on Sails Server. I believe waves are persistent on this server.<br>
<br>
PyGoWave<br>
<a href="http://pygowave.net" target="_blank">http://pygowave.net</a><br>
This was an early effort to build a Wave Server in Python. Last I knew<br>
PyGoWave did not Federate or talk with other clients. I believe the waves<br>
are persistent.<br>
<br>
Both FedOne and Ruby on Sails require that you have an XMPP server up and<br>
running. I've been using the OpenFire XMPP server, although I've heard<br>
others have had success with jabberd and Prosody.<br>
<br>
Hope this helps. I'd love to chat about collaborating. Adding Wave<br>
capabilities to Naali sounds especially interesting.<br>
<font color="#888888"><br>
Aldon<br>
</font><div><div></div><div class="h5"><br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</a><br>
[mailto:<a href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</a>]On Behalf Of Jeroen van<br>
Veen<br>
Sent: Saturday, December 05, 2009 8:20 AM<br>
To: <a href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</a><br>
Subject: Re: [Opensim-dev] Opensim Wave?<br>
<br>
<br>
Hello,<br>
<br>
Is the google wave server component open sourced as well? I read somewhere<br>
that only the wave protocol is open, and that google will be the only<br>
service<br>
provider for now. Concerning functionality, i personally like the idea of a<br>
realtime collaborative text editor for the web. When it comes to this<br>
functionality, the libinfinote library(lgpl) from the gobby project may be<br>
interesting. It's then just a matter of creating a js-client with orbited as<br>
comet server, and later switch to websockets when they are supported by the<br>
main browsers.<br>
<br>
With ogre as the renderer in Naali, it may be not so much work to integrate<br>
an<br>
in-world awesomium browser that uses this technology.<br>
<br>
Jeroen<br>
<br>
<br>
Op zaterdag 05 december 2009 02:21:43 schreef Rich White:<br>
> XMPP/Jabber are also supported by OpenCobalt so further support of<br>
> XMPP by Opensim could prove to be a starting point to virtual world<br>
> convergence with regard to platforms. A bit more here -<br>
> <a href="http://roots.greenbush.us/?p=867" target="_blank">http://roots.greenbush.us/?p=867</a><br>
><br>
> Cheers,<br>
> Rich<br>
> ==<br>
><br>
> On Fri, Dec 4, 2009 at 5:33 PM, Aldon Hynes<br>
><br>
> <<a href="mailto:Aldon.Hynes@orient-lodge.com">Aldon.Hynes@orient-lodge.com</a>> wrote:<br>
> > Okay, I must admit I've mostly been sitting on the sidelines recently.<br>
I<br>
> > still have OpenSim 0.5 installed on a computer or two...<br>
> ><br>
> > Anyway, there have been some interesting discussions recently about<br>
> > Second Life - Google Wave integration. Much of it is focused on the<br>
fact<br>
> > that Google Wave runs as a XMPP component (XEP-114). I seem to recall<br>
> > there had been some work with OpenSim/XMPP. Looking at it, it looks<br>
like<br>
> > OpenSim/XMPP is focused on OpenSim as an XMPP client instead of an XMPP<br>
> > component.<br>
> ><br>
> > Are there people around interested in OpenSim/Wave connectivity?<br>
> > Thoughts about what that might look like? Drop me a note if your<br>
> > interested.<br>
> ><br>
> > I do have a FedOne Wave server running and have been testing different<br>
> > clients and would love to share ideas.<br>
> ><br>
> > Aldon<br>
> > _______________________________________________<br>
> > Opensim-dev mailing list<br>
> > <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
> > <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
><br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</div></div></blockquote></div><br>