You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Filip Hanik - Dev Lists <de...@hanik.com> on 2007/06/07 15:08:02 UTC

Bayeux implementation

yo,
I was gonna create a Bayeux implementation for Tomcat,
I am thinking it might be good for us to work with the Jetty and 
Glassfish folks to use the same org.dojox interfaces.

Question: Where should I do this, sandbox or trunk?

Why Bayeux? Cause there is a good client support through the Dojo toolkit.

Thoughts?

Filip

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Re: Bayeux implementation

Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
Yoav Shapira wrote:
> Hey,
>
> On 6/7/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
>> yo,
>> I was gonna create a Bayeux implementation for Tomcat,
>> I am thinking it might be good for us to work with the Jetty and
>> Glassfish folks to use the same org.dojox interfaces.
>
> I like the idea!
>
>> Question: Where should I do this, sandbox or trunk?
>
> For something this experimental, probably the sandbox, but I could see
> it going either way.
so is trunk until we agree or agree to disagree :)

Filip

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Re: Bayeux implementation

Posted by Yoav Shapira <yo...@apache.org>.
Hey,

On 6/7/07, Filip Hanik - Dev Lists <de...@hanik.com> wrote:
> yo,
> I was gonna create a Bayeux implementation for Tomcat,
> I am thinking it might be good for us to work with the Jetty and
> Glassfish folks to use the same org.dojox interfaces.

I like the idea!

> Question: Where should I do this, sandbox or trunk?

For something this experimental, probably the sandbox, but I could see
it going either way.

Yoav

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Re: Bayeux implementation

Posted by Remy Maucherat <re...@apache.org>.
Filip Hanik - Dev Lists wrote:
> If the spec is bad, then its another reason for us to join in, but the 
> fact that there is a client support, speaks for itself.

Specifically, the syntax looks funny to me, and the spec document is bad 
(that's what I meant with "the spec is bad"). Implementing it doesn't hurt.

Rémy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Re: Bayeux implementation

Posted by Remy Maucherat <re...@apache.org>.
Peter Rossbach wrote:
> OK, really the current "spec doc" is strange, but it's good enough  to 
> start discussions. Please, let us start talks with other
> Bayeux folks.

I don't like the syntax much more than the "spec doc" (lol, not ready 
yet for the IETF, I guess), but it's an implementation detail that the 
user is not supposed to see, so I guess this stuff is all good then ;)

Rémy


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Re: Bayeux implementation

Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
here is a summary of what needs to be done

1. The basic Java API that we want to work around is
http://fisheye.codehaus.org/browse/jetty-contrib/jetty/trunk/contrib/cometd/src/main/java/dojox/cometd

2. Implement a JSON parser in Java, or grab another one,

3. Implement the API in step 1) using the Tomcat Comet model.

4. And a build script, that downloads the dependencies (like step 1) and 
other if needed, and build the stuff

It's pretty straight forward

Filip

Peter Rossbach wrote:
> Hi Filip,
>
> Great, I think it is a good time to start talking about Bayeux /dojo 
> as a standard comet protocol. The current different Async/comet server 
> API's  make it very strong to start for most programmers. I review the 
> Jetty Bayeux implementation and find it very useful.
> OK, really the current "spec doc" is strange, but it's good enough  to 
> start discussions. Please, let us start talks with other
> Bayeux folks.
>
> How can I help?
>
> Peter
>
> +1: to start bayeux implementation at a sandbox.
>
>
> Am 07.06.2007 um 16:15 schrieb Filip Hanik - Dev Lists:
>
>> Remy Maucherat wrote:
>>> Filip Hanik - Dev Lists wrote:
>>>> yo,
>>>> I was gonna create a Bayeux implementation for Tomcat,
>>>> I am thinking it might be good for us to work with the Jetty and 
>>>> Glassfish folks to use the same org.dojox interfaces.
>>>
>>> I don't like dependencies ;) I am not interested in working with 
>>> these two projects, which had relationships with Tomcat in the past, 
>>> but chose to end them.
>> not working with the projects is your personal prerogative, the rest 
>> of the community might not be against it. I am not and one more post 
>> thought it was a good idea.
>> I think the relationships especially around bayeux can be very 
>> beneficial for all of us, as we can be part of it dictating the 
>> direction of it instead of just having to respond to it due to user 
>> demand.
>> I'd like to know if anyone else is strongly against it, since I don't 
>> think past events should dictate if we join this initiative or not.
>>>> Question: Where should I do this, sandbox or trunk?
>>>
>>> Sandbox, I think.
>> Sandbox it is.
>>>
>>>> Why Bayeux? Cause there is a good client support through the Dojo 
>>>> toolkit.
>>>
>>> I was wondering if it was a standard, so I guess client support is a 
>>> benefit. However, the spec itself looks bad at the moment (unless I 
>>> missed something).
>> If the spec is bad, then its another reason for us to join in, but 
>> the fact that there is a client support, speaks for itself.
>> Comet is very popular but the skillset to create a client that works 
>> in a browser is hard to find. This was very much the feedback we got 
>> during Apachecon EU in Amsterdam.
>>
>> Whether we use it or not, we can decide on later. In the meantime 
>> I'll touch base with the folks and get the ball rolling.
>>
>> Filip
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: dev-help@tomcat.apache.org
>>
>>
>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition. 
> Version: 7.5.472 / Virus Database: 269.8.11/837 - Release Date: 6/6/2007 2:03 PM
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Re: Bayeux implementation

Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
Peter Rossbach wrote:
> Hi Filip,
>
> Great, I think it is a good time to start talking about Bayeux /dojo 
> as a standard comet protocol. The current different Async/comet server 
> API's  make it very strong to start for most programmers. I review the 
> Jetty Bayeux implementation and find it very useful.
> OK, really the current "spec doc" is strange, but it's good enough  to 
> start discussions. Please, let us start talks with other
> Bayeux folks.
Yes, got the ball rolling on this one.
>
> How can I help?
Feel free to join in on the implementation/coding. Once we have the Java 
APIs, we'll create the implementation on top of Tomcat Comet,

Filip
>
> Peter
>
> +1: to start bayeux implementation at a sandbox.
>
>
> Am 07.06.2007 um 16:15 schrieb Filip Hanik - Dev Lists:
>
>> Remy Maucherat wrote:
>>> Filip Hanik - Dev Lists wrote:
>>>> yo,
>>>> I was gonna create a Bayeux implementation for Tomcat,
>>>> I am thinking it might be good for us to work with the Jetty and 
>>>> Glassfish folks to use the same org.dojox interfaces.
>>>
>>> I don't like dependencies ;) I am not interested in working with 
>>> these two projects, which had relationships with Tomcat in the past, 
>>> but chose to end them.
>> not working with the projects is your personal prerogative, the rest 
>> of the community might not be against it. I am not and one more post 
>> thought it was a good idea.
>> I think the relationships especially around bayeux can be very 
>> beneficial for all of us, as we can be part of it dictating the 
>> direction of it instead of just having to respond to it due to user 
>> demand.
>> I'd like to know if anyone else is strongly against it, since I don't 
>> think past events should dictate if we join this initiative or not.
>>>> Question: Where should I do this, sandbox or trunk?
>>>
>>> Sandbox, I think.
>> Sandbox it is.
>>>
>>>> Why Bayeux? Cause there is a good client support through the Dojo 
>>>> toolkit.
>>>
>>> I was wondering if it was a standard, so I guess client support is a 
>>> benefit. However, the spec itself looks bad at the moment (unless I 
>>> missed something).
>> If the spec is bad, then its another reason for us to join in, but 
>> the fact that there is a client support, speaks for itself.
>> Comet is very popular but the skillset to create a client that works 
>> in a browser is hard to find. This was very much the feedback we got 
>> during Apachecon EU in Amsterdam.
>>
>> Whether we use it or not, we can decide on later. In the meantime 
>> I'll touch base with the folks and get the ball rolling.
>>
>> Filip
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: dev-help@tomcat.apache.org
>>
>>
>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition. 
> Version: 7.5.472 / Virus Database: 269.8.11/837 - Release Date: 6/6/2007 2:03 PM
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Re: Bayeux implementation

Posted by Peter Rossbach <pr...@objektpark.de>.
Hi Filip,

Great, I think it is a good time to start talking about Bayeux /dojo  
as a standard comet protocol. The current different Async/comet  
server API's  make it very strong to start for most programmers. I  
review the Jetty Bayeux implementation and find it very useful.
OK, really the current "spec doc" is strange, but it's good enough   
to start discussions. Please, let us start talks with other
Bayeux folks.

How can I help?

Peter

+1: to start bayeux implementation at a sandbox.


Am 07.06.2007 um 16:15 schrieb Filip Hanik - Dev Lists:

> Remy Maucherat wrote:
>> Filip Hanik - Dev Lists wrote:
>>> yo,
>>> I was gonna create a Bayeux implementation for Tomcat,
>>> I am thinking it might be good for us to work with the Jetty and  
>>> Glassfish folks to use the same org.dojox interfaces.
>>
>> I don't like dependencies ;) I am not interested in working with  
>> these two projects, which had relationships with Tomcat in the  
>> past, but chose to end them.
> not working with the projects is your personal prerogative, the  
> rest of the community might not be against it. I am not and one  
> more post thought it was a good idea.
> I think the relationships especially around bayeux can be very  
> beneficial for all of us, as we can be part of it dictating the  
> direction of it instead of just having to respond to it due to user  
> demand.
> I'd like to know if anyone else is strongly against it, since I  
> don't think past events should dictate if we join this initiative  
> or not.
>>> Question: Where should I do this, sandbox or trunk?
>>
>> Sandbox, I think.
> Sandbox it is.
>>
>>> Why Bayeux? Cause there is a good client support through the Dojo  
>>> toolkit.
>>
>> I was wondering if it was a standard, so I guess client support is  
>> a benefit. However, the spec itself looks bad at the moment  
>> (unless I missed something).
> If the spec is bad, then its another reason for us to join in, but  
> the fact that there is a client support, speaks for itself.
> Comet is very popular but the skillset to create a client that  
> works in a browser is hard to find. This was very much the feedback  
> we got during Apachecon EU in Amsterdam.
>
> Whether we use it or not, we can decide on later. In the meantime  
> I'll touch base with the folks and get the ball rolling.
>
> Filip
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>


Re: Bayeux implementation

Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
Remy Maucherat wrote:
> Filip Hanik - Dev Lists wrote:
>> yo,
>> I was gonna create a Bayeux implementation for Tomcat,
>> I am thinking it might be good for us to work with the Jetty and 
>> Glassfish folks to use the same org.dojox interfaces.
>
> I don't like dependencies ;) I am not interested in working with these 
> two projects, which had relationships with Tomcat in the past, but 
> chose to end them.
not working with the projects is your personal prerogative, the rest of 
the community might not be against it. I am not and one more post 
thought it was a good idea.
I think the relationships especially around bayeux can be very 
beneficial for all of us, as we can be part of it dictating the 
direction of it instead of just having to respond to it due to user demand.
I'd like to know if anyone else is strongly against it, since I don't 
think past events should dictate if we join this initiative or not.
>> Question: Where should I do this, sandbox or trunk?
>
> Sandbox, I think.
Sandbox it is.
>
>> Why Bayeux? Cause there is a good client support through the Dojo 
>> toolkit.
>
> I was wondering if it was a standard, so I guess client support is a 
> benefit. However, the spec itself looks bad at the moment (unless I 
> missed something).
If the spec is bad, then its another reason for us to join in, but the 
fact that there is a client support, speaks for itself.
Comet is very popular but the skillset to create a client that works in 
a browser is hard to find. This was very much the feedback we got during 
Apachecon EU in Amsterdam.

Whether we use it or not, we can decide on later. In the meantime I'll 
touch base with the folks and get the ball rolling.

Filip

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Re: Bayeux implementation

Posted by Remy Maucherat <re...@apache.org>.
Filip Hanik - Dev Lists wrote:
> yo,
> I was gonna create a Bayeux implementation for Tomcat,
> I am thinking it might be good for us to work with the Jetty and 
> Glassfish folks to use the same org.dojox interfaces.

I don't like dependencies ;) I am not interested in working with these 
two projects, which had relationships with Tomcat in the past, but chose 
to end them.

> Question: Where should I do this, sandbox or trunk?

Sandbox, I think.

> Why Bayeux? Cause there is a good client support through the Dojo toolkit.

I was wondering if it was a standard, so I guess client support is a 
benefit. However, the spec itself looks bad at the moment (unless I 
missed something).

Rémy


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org