incubator-wave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Grobmeier <>
Subject Re: Is Wave ready for integration?
Date Mon, 25 Jun 2012 14:27:11 GMT
On Mon, Jun 25, 2012 at 3:46 PM, Michael MacFadden
<> wrote:
> Christian,
> I think the take away from Kune is the example of integration rather than the functionality
Kune provides.

Oh. Thanks.

> What is the basic architecture of your application?  Is it web based? Java? Maven or
Ant builds? etc.

Its a Java app, built with Struts 2 and Cayenne (mostly Apache
products used, natural to me). Buildsystem is Maven.
The frontend contains tons of JavaScript and I am not afraid to add
more, if necessary.
The whole thing is web based. It has additional mobile apps, but so
far I do not plan to show Apache Wave there, but of course
this is an interesting idea for the future.

You can say, except with some nasty stuff my whole app is pretty
straightforward and nothing "extraordinary" like huge datapool or
excessive calculations or such.


> ~Michael
> P.S. Feel free to ping me off list if you like.
> On Jun 25, 2012, at 6:21 AM, Christian Grobmeier wrote:
>> On Mon, Jun 25, 2012 at 1:29 PM, Yuri Z <> wrote:
>>> What you describe sounds very similar to - you might want
>>> to take a look at it.
>> Thanks for the link. I am not sure about Kune. It offers so much that
>> I am not sure i will ever get that integrated well.
>> Reading:
>> It says AWave is focussing on "my inbox" while Kune focusses on
>> Documents, Tasks etc.
>> I don't want the latter stuff, just the "communication" aka "inbox".
>> Apache Wave looks more straightforward to me at the moment without
>> much overhead. As Kune is based on Apache Wave, my feeling says its
>> better to use just Wave and extend it to exactly my needs.
>>> On Mon, Jun 25, 2012 at 2:05 PM, Christian Grobmeier <>wrote:
>>>> Hello guys,
>>>> I am following this list not only because I am interested from a asf
>>>> members perspective. I plan to utilize Wave in my own app. Now I
>>>> slowly reach the state were I could integrate it and need a few
>>>> pointers if Wave is already ready for that.
>>>> My plan:
>>>> - when an user activates a special "team" module in my app, a new
>>>> rider should be available. It should contain the Wave client
>>>> - user a is known with his email address. In the first version, only
>>>> communication between users of my app should be allowed (need to make
>>>> sure the load isn't killing me)
>>>> Questions:
>>>> - How difficult is it to integrate a client into my own app? I don't
>>>> want to open a separate window or something, it should integrate into
>>>> my stuff and contain my look&feel
>>>> - how stable is the Wave server? Is it already ok for a limited user
>>>> base, lets say 5000 people (many of them not so much active)
>>>> - is somebody here available for contracting and can help me with this
>>>> job? As I run only a small company I am glad about good rates and
>>>> would be willing to give back all necessary changes to the community.
>>>> If somebody is avail, please ping me offlist (or send a recommendation
>>>> offlist).
>>>> Thanks!
>>>> Christian
>>>> --
>> --


View raw message