You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Halil Karakose <ha...@gmail.com> on 2010/11/07 00:27:46 UTC
cometd in tapestry 5
Hi,
I found that tacos supports cometd for tapestry 4. What about tapestry 5?
Does tapestry support cometd?
thanks
Re: cometd in tapestry 5
Posted by françois facon <fr...@gmail.com>.
During Devoxx 2010 Atmopshere was mention a least in 3 conference.
Paul Sandoz plan to use it for http streaming in jax-rs.
There is some implementation for Web FWK like JSF and
Wicket<http://jfarcand.wordpress.com/2010/10/07/writing-websocket-application-using-apache-wicket/>
.
Le 7 novembre 2010 11:31, françois facon <fr...@gmail.com> a écrit :
> Atmosphere looks very fine.
> I guess that Atmosphere Meteor could be use to
easily
add
asynchronous
> support to Tapestry.
> For the client side Atmopshere also provide prototype object an jQuery
> Plugin.
>
>
> 2010/11/7 Robert R. Sanders <ro...@ipov.net>
>
> I would think some integration for a high/medium level framework like
>> atmosphere, or the dojo CometD api could potentially avoid tying T5 to a
>> specific server.
>>
>>
>> On 11/6/2010 7:11 PM, Howard Lewis Ship wrote:
>>
>>> Not at this time, perhaps in 5.3. I know I'd use that capability if it
>>> was
>>> available, even if it tied Tapestry to Jetty specifically.
>>>
>>> On Sat, Nov 6, 2010 at 4:27 PM, Halil Karakose<halilkarakose@gmail.com
>>> >wrote:
>>>
>>> Hi,
>>>> I found that tacos supports cometd for tapestry 4. What about tapestry
>>>> 5?
>>>> Does tapestry support cometd?
>>>>
>>>> thanks
>>>>
>>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
Re: cometd in tapestry 5
Posted by françois facon <fr...@gmail.com>.
Atmosphere looks very fine.
I guess that Atmosphere Meteor could be use to
easily
add
asynchronous
support to Tapestry.
For the client side Atmopshere also provide prototype object an jQuery
Plugin.
2010/11/7 Robert R. Sanders <ro...@ipov.net>
> I would think some integration for a high/medium level framework like
> atmosphere, or the dojo CometD api could potentially avoid tying T5 to a
> specific server.
>
>
> On 11/6/2010 7:11 PM, Howard Lewis Ship wrote:
>
>> Not at this time, perhaps in 5.3. I know I'd use that capability if it
>> was
>> available, even if it tied Tapestry to Jetty specifically.
>>
>> On Sat, Nov 6, 2010 at 4:27 PM, Halil Karakose<halilkarakose@gmail.com
>> >wrote:
>>
>> Hi,
>>> I found that tacos supports cometd for tapestry 4. What about tapestry
>>> 5?
>>> Does tapestry support cometd?
>>>
>>> thanks
>>>
>>>
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: cometd in tapestry 5
Posted by françois facon <fr...@gmail.com>.
Dojo seem's to provide an API that looks like WebSocket, and fallback to
other techniques if WebSocket isn’t available.
http://www.sitepen.com/blog/2010/10/31/dojo-websocket/
If you want to provided a real bi directionnal data channel between your
server and your client,
you will need a gateway that can manage protocoles like
-cometd,
-flash (rtmpt protocole),
- ajax long polling
- websocket
Kaazing provided this kind of gateway and they say (
http://tech.kaazing.com/documentation/faq.html#bayeux
"Most Comet implementations rely on the Bayeux protocol, which requires
messages from the origin to be transformed to conform to the Bayeux
protocol. This transformation introduces unnecessary complexity in your
system, requiring developers to manipulate one message format on the server
(for example, JMS, IMAP, and XMPP) and a second message format (for example,
Bayeux or JSON) on the client. Bayeux also introduces an unnecessary
performance overhead to your system by forcing a message to be interpreted
and processed prior to being sent over the wire. With WebSocket, the message
sent by the server is the same message that is delivered to the browser,
eliminating the complexity and performance concerns introduced by
transformation code."
We use the same approach for our gateway. We also feel like WebSocket will
replace cometD even if we don't know IE9 status about WebSocket.
2010/11/7 Alessio Gambi <ag...@gmail.com>
> I used the DWR 2.0 and it worked fine.
> But I did not really liked the solution for some reasons:
> - you need to add the DWR servlet along tapestry and do some "tricks" to
> forward the dwr calls to it while tapestry maintains the state of your
> application.
> - the solution was too *framework specific* while it should be better to
> have some generic service and different implementations.(like prototype for
> js as an example)
> - DWR is mainly about implementing RPC with JavaScript and the "reverse
> Ajax" is only one of its features. I do not known if it so right to "import"
> the entire framework just to have it.
>
> -- Alessio
>
> On 7-nov-2010, at 04:22, "Robert R. Sanders" <ro...@ipov.net>
> wrote:
>
> > I would think some integration for a high/medium level framework like
> atmosphere, or the dojo CometD api could potentially avoid tying T5 to a
> specific server.
> >
> > On 11/6/2010 7:11 PM, Howard Lewis Ship wrote:
> >> Not at this time, perhaps in 5.3. I know I'd use that capability if it
> was
> >> available, even if it tied Tapestry to Jetty specifically.
> >>
> >> On Sat, Nov 6, 2010 at 4:27 PM, Halil Karakose<halilkarakose@gmail.com
> >wrote:
> >>
> >>> Hi,
> >>> I found that tacos supports cometd for tapestry 4. What about tapestry
> 5?
> >>> Does tapestry support cometd?
> >>>
> >>> thanks
> >>>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
Re: cometd in tapestry 5
Posted by Alessio Gambi <ag...@gmail.com>.
I used the DWR 2.0 and it worked fine.
But I did not really liked the solution for some reasons:
- you need to add the DWR servlet along tapestry and do some "tricks" to forward the dwr calls to it while tapestry maintains the state of your application.
- the solution was too *framework specific* while it should be better to have some generic service and different implementations.(like prototype for js as an example)
- DWR is mainly about implementing RPC with JavaScript and the "reverse Ajax" is only one of its features. I do not known if it so right to "import" the entire framework just to have it.
-- Alessio
On 7-nov-2010, at 04:22, "Robert R. Sanders" <ro...@ipov.net> wrote:
> I would think some integration for a high/medium level framework like atmosphere, or the dojo CometD api could potentially avoid tying T5 to a specific server.
>
> On 11/6/2010 7:11 PM, Howard Lewis Ship wrote:
>> Not at this time, perhaps in 5.3. I know I'd use that capability if it was
>> available, even if it tied Tapestry to Jetty specifically.
>>
>> On Sat, Nov 6, 2010 at 4:27 PM, Halil Karakose<ha...@gmail.com>wrote:
>>
>>> Hi,
>>> I found that tacos supports cometd for tapestry 4. What about tapestry 5?
>>> Does tapestry support cometd?
>>>
>>> thanks
>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: cometd in tapestry 5
Posted by "Robert R. Sanders" <ro...@ipov.net>.
I would think some integration for a high/medium level framework like
atmosphere, or the dojo CometD api could potentially avoid tying T5 to a
specific server.
On 11/6/2010 7:11 PM, Howard Lewis Ship wrote:
> Not at this time, perhaps in 5.3. I know I'd use that capability if it was
> available, even if it tied Tapestry to Jetty specifically.
>
> On Sat, Nov 6, 2010 at 4:27 PM, Halil Karakose<ha...@gmail.com>wrote:
>
>> Hi,
>> I found that tacos supports cometd for tapestry 4. What about tapestry 5?
>> Does tapestry support cometd?
>>
>> thanks
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: cometd in tapestry 5
Posted by Howard Lewis Ship <hl...@gmail.com>.
Not at this time, perhaps in 5.3. I know I'd use that capability if it was
available, even if it tied Tapestry to Jetty specifically.
On Sat, Nov 6, 2010 at 4:27 PM, Halil Karakose <ha...@gmail.com>wrote:
> Hi,
> I found that tacos supports cometd for tapestry 4. What about tapestry 5?
> Does tapestry support cometd?
>
> thanks
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to learn
how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com