Re: Google Wave - anyone?

2009-07-30 Thread Scott Wilson
Yes, Wookie is a server-side Widget repository and runtime/state  
management application that implements the Google Wave Gadget APIs; it  
has an API for connecting to applications that manage participants and  
contexts, which can include waves but also traditional CMS and  
intranet groups etc. So it could plug into a Wave Server (c) to handle  
the gadget management task.


S

On 30 Jul 2009, at 06:55, Bernd Fondermann wrote:


On Wed, Jul 29, 2009 at 15:58, Scott
Wilsonscott.bradley.wil...@gmail.com wrote:
Wookie implements the Wave Gadget API, which is one part of a  
Google Wave

system, but not the Wave Protocol itself.

It might be interesting if Vysper could make use of Wookie for the  
wave

gadgets part.


Is Wookie a server-side technology? Otherwise I don't see the link
between both.
Maybe it could be the other way round (Wookie using Vysper), if Wookie
makes use of the XMPP protocol.

Of course, when it comes to implementing Wave, all projects should  
join efforts.


Here is a short wrap-up of what you need to implement Wave:
+ a Wave client - this is a very fat client, and it's also a XMPP  
client

+ a server-side Wave Provider, consisting of
 (a.) Network Server(s)
 (b.) Wave Store
 (c.) Wave Server

In this setup, I'd see (a.) as a XMPP server running the Wave Protocol
(an extension of XMPP), probably tunneling through HTTP[2]. Compared
to implementing XMPP, implementing the Wave protocol extension should
be relatively easy.
The hard and critical part is definitively (c.), with all the
Operational Transformation stuff going on. Google starts open sourcing
this at [1].

[1] http://code.google.com/p/wave-protocol/
[2] http://xmpp.org/extensions/xep-0124.html

  Bernd



S

On 29 Jul 2009, at 12:24, Emmanuel Lecharny wrote:


Christian Grobmeier wrote:


Hi,


Hi,


I know my request might be a bit unusual, but is somebody here
preparing an idea for implementing the Google Wave Protocol? I  
might

want to follow, if somebody does.



You may ask Bernd Fondermann about that. He has started a project  
called

Vysper (http://mina.apache.org/vysper) which is a XMPP server


--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org






-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org





smime.p7s
Description: S/MIME cryptographic signature


Re: Google Wave - anyone?

2009-07-30 Thread Christian Grobmeier
 Yes, Wookie is a server-side Widget repository and runtime/state management
 application that implements the Google Wave Gadget APIs; it has an API for
 connecting to applications that manage participants and contexts, which can
 include waves but also traditional CMS and intranet groups etc. So it could
 plug into a Wave Server (c) to handle the gadget management task.

How complicated would it be to extend Vysper to a Wave Server? I am
not deep into Jabber but I think Googles Wave might be one of the next
(big) cool things. I am willing to learn and help if other people are
interested.

Is it possible to build some kind of wave client build on top of wookie?
Btw, it feels that wookie is quite similar to Apache Shindig - is it?

Best,
Christian

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Google Wave - anyone?

2009-07-30 Thread Bernd Fondermann
On Thu, Jul 30, 2009 at 13:30, Christian Grobmeiergrobme...@gmail.com wrote:
 Yes, Wookie is a server-side Widget repository and runtime/state management
 application that implements the Google Wave Gadget APIs; it has an API for
 connecting to applications that manage participants and contexts, which can
 include waves but also traditional CMS and intranet groups etc. So it could
 plug into a Wave Server (c) to handle the gadget management task.

 How complicated would it be to extend Vysper to a Wave Server?

As I tried to outline before: The Google Wave protocol, as a XMPP
extension, should be relatively easy to implement.
We have Message-type stanzas and we are working on the PubSub
extension right now, which is needed by the GW-XEP.

Implementing the 'rest' of the Wave Provider/Wave Server is a bit more
sophisticated job and does not require XMPP Know-How.

  Bernd

 I am
 not deep into Jabber but I think Googles Wave might be one of the next
 (big) cool things. I am willing to learn and help if other people are
 interested.

you'll find us on d...@mina.apache.org. see you there...


 Is it possible to build some kind of wave client build on top of wookie?
 Btw, it feels that wookie is quite similar to Apache Shindig - is it?

From the Wookie Proposal:
For example, it[the Wookie engine] leverages Apache Shindig
(Incubating) to render OpenSocial gadgets.

  Bernd

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Google Wave - anyone?

2009-07-30 Thread Ian Boston


On 30 Jul 2009, at 12:30, Christian Grobmeier wrote:


Btw, it feels that wookie is quite similar to Apache Shindig - is it?


IIUC, Wookie contains Shindig to provide OpenSocial Gadget Rendering  
and I would assume the OpenSocial API. Wookie also contains a W3C  
gadget renderer.


Ian

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: Google Wave - anyone?

2009-07-30 Thread Sylvain Wallez

Christian Grobmeier wrote:

Yes, Wookie is a server-side Widget repository and runtime/state management
application that implements the Google Wave Gadget APIs; it has an API for
connecting to applications that manage participants and contexts, which can
include waves but also traditional CMS and intranet groups etc. So it could
plug into a Wave Server (c) to handle the gadget management task.



How complicated would it be to extend Vysper to a Wave Server? I am
not deep into Jabber but I think Googles Wave might be one of the next
(big) cool things. I am willing to learn and help if other people are
interested.
  


If you look at Wave's white papers and draft protocol specifications [1] 
there's a lot more in a Wave server than XMPP.


A Wave server is firstly a document repository that handles concurrent 
editing by storing/applying/merging transformation operations on these 
documents. XMPP is there to allow federation, i.e. allowing people from 
different wave domains to collaborate on the same documents. In this 
regard, XMPP in Wave is essentially a transport protocol for 
transformation operations.



Is it possible to build some kind of wave client build on top of wookie?
  


No. Wookie addresses a particular aspect of a Wave server, which is some 
additional APIs for collaborative OpenSocial gadgets [2]



Btw, it feels that wookie is quite similar to Apache Shindig - is it?
  


Wookie complements Shinding with an implementation of the Wave gadget API.

Hope this makes things clearer.

Sylvain

[1] http://www.waveprotocol.org/
[2] http://code.google.com/apis/wave/extensions/gadgets/guide.html

--
Sylvain Wallez - http://bluxte.net


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Fwd: foundation: r18818 - /documents/received/eFax-747715537.pdf

2009-07-30 Thread Craig L Russell

Hi,

We just received a fax from FAX-SJC-101-TDM that came in ruined.

The first page is completely unreadable except for the country: USA.

The second page came in ok but I can't decipher the signature.

If anyone knows who sent this fax, please contact them to resend it.

Craig

Begin forwarded message:


From: ru...@apache.org
Date: July 30, 2009 3:04:23 PM PDT
To: foundation-...@apache.org
Subject: foundation: r18818 - /documents/received/eFax-747715537.pdf
Reply-To: memb...@apache.org

Author: rubys
Date: Thu Jul 30 22:04:22 2009
New Revision: 18818

Log:
Subject: eFax message from FAX-SJC-101-TDM - 2 page(s), Caller-ID:  
11010

From: eFax mess...@inbound.efax.com
Date: Thu, 30 Jul 2009 21:58:59 +
Message-Id: 200907302159.n6ulxbkw021...@media2.atl1.colo.j2noc.com

Added:
   documents/received/eFax-747715537.pdf   (with props)

Added: documents/received/eFax-747715537.pdf
= 
= 
= 
= 
= 
= 
= 
= 
==

Binary file - no diff available.

Propchange: documents/received/eFax-747715537.pdf
--
   svn:mime-type = application/pdf




Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@sun.com
P.S. A good JDO? O, Gasp!



smime.p7s
Description: S/MIME cryptographic signature