Re: [RT] The block protocol

Le 5 avr. 05, à 04:42, Ralph Goers a écrit : ...When the email gets to be long or quotes previous nested emails in their entirety I tend to just move on and ignore the post... FWIW, it is exactly my case: not enough time to follow these lng emails. The mailing-list discussion mode makes it v

Re: [RT] The block protocol

Daniel Fagerstrom wrote: is resolved in the same way as an ordinary external block URI. To make this possible the role of being a super block must be identifiable among the connections in the wiring info. Maybe by reserving the name "super" for this case. WDYT? /Daniel A few thoughts here (tha

Re: [RT] The block protocol

Daniel Fagerstrom wrote: --- o0o --- Just some sidenotes... The main involved components are the BlocksManager that in turn has access to one BlockManager for each block. (From [1] BlockManager is the ServiceManager of the block) Block local access --

Re: RFC-2396 (Was: Re: [RT] composition vs. inheritance in blocks)

Daniel Fagerstrom wrote: Colin Paul Adams wrote: "Pier" == Pier Fumagalli <[EMAIL PROTECTED]> writes: Pier> I'm already slightly "upset" about the "cocoon://" protocol, Pier> as it does not follow the URI RFC properly, I'd like to Pier> address the problem as early as possible.

Re: RFC-2396 (Was: Re: [RT] composition vs. inheritance in blocks)

Pier Fumagalli wrote: The only problem I have with "block:super://blah.xml" is that "//" in an URI indicates the start of the authority part, and this is defined as "[EMAIL PROTECTED]:port", and no matter how you see it, "block:...anything..." _is_ a URI, and thus should follow its spec...

Re: [RT] composition vs. inheritance in blocks

Daniel Fagerstrom wrote: As Stefano doesn't work fulltime at Cocoon anymore, the rest of us must take our reponsibilty and make shure that our individual ideas actually intgrates with others ideas and are benefical for Cocoon as a whole. Daniel, I have never worked fulltime on Cocoon and I have a

Re: What is the community looking for?

Hi Sylvain, Let me start by saying I have no desire to precipitate a fate such as this for the Cocoon community: Instead, this is what I want: I want to find richer and better ways for online

DO NOT REPLY [Bug 34294] - [PATCH] Use htmlunit to test Cocoon samples (replacing anteater tests)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34294] New: - [PATCH] Use htmlunit to test Cocoon samples (replacing anteater tests)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

[RT] The block protocol (was: RFC-2396)

Daniel Fagerstrom wrote: Pier Fumagalli wrote: On 4 Apr 2005, at 16:26, Daniel Fagerstrom wrote: Pier Fumagalli wrote: On 31 Mar 2005, at 01:26, Stefano Mazzocchi wrote: block:super://blah.xml A very simple remark, I don't want to criticise... I'm already slightly "upset" about the "cocoon://" pro

Re: RFC-2396 (Was: Re: [RT] composition vs. inheritance in blocks)

Colin Paul Adams wrote: "Daniel" == Daniel Fagerstrom <[EMAIL PROTECTED]> writes: Daniel> cocoon:foo/bar Daniel> where "foo/bar" is called a root less path. But I don't Daniel> find any explanation about what it is supposed to mean. Well, it could mean anything the protocol inventor

add deprecation note to http://cocoon.apache.org/2.1/userdocs/xsp/index.html

i would suggest to add a deprecation note to the XSP documentation and point to newer technologies. it makes me squirm to see all these xsp questions by cocoon beginners who should proably use flow/cforms/jx just a thought, -gregor

Re: RFC-2396 (Was: Re: [RT] composition vs. inheritance in blocks)

> "Daniel" == Daniel Fagerstrom <[EMAIL PROTECTED]> writes: Daniel> cocoon:foo/bar Daniel> where "foo/bar" is called a root less path. But I don't Daniel> find any explanation about what it is supposed to mean. Well, it could mean anything the protocol inventor intended. Not al

Re: RFC-2396 (Was: Re: [RT] composition vs. inheritance in blocks)

On 4 Apr 2005, at 18:09, Colin Paul Adams wrote: "Pier" == Pier Fumagalli <[EMAIL PROTECTED]> writes: Pier> I'm already slightly "upset" about the "cocoon://" protocol, Pier> as it does not follow the URI RFC properly, I'd like to Pier> address the problem as early as possible... Pi

Re: RFC-2396 (Was: Re: [RT] composition vs. inheritance in blocks)

Colin Paul Adams wrote: "Pier" == Pier Fumagalli <[EMAIL PROTECTED]> writes: Pier> I'm already slightly "upset" about the "cocoon://" protocol, Pier> as it does not follow the URI RFC properly, I'd like to Pier> address the problem as early as possible... Pier> http://www.i

Re: RFC-2396 (Was: Re: [RT] composition vs. inheritance in blocks)

> "Pier" == Pier Fumagalli <[EMAIL PROTECTED]> writes: Pier> I'm already slightly "upset" about the "cocoon://" protocol, Pier> as it does not follow the URI RFC properly, I'd like to Pier> address the problem as early as possible... Pier> http://www.ietf.org/rfc/rfc2396.txt

Re: RFC-2396 (Was: Re: [RT] composition vs. inheritance in blocks)

Pier Fumagalli wrote: On 4 Apr 2005, at 16:26, Daniel Fagerstrom wrote: Pier Fumagalli wrote: On 31 Mar 2005, at 01:26, Stefano Mazzocchi wrote: block:super://blah.xml A very simple remark, I don't want to criticise... I'm already slightly "upset" about the "cocoon://" protocol, as it does not f

Re: RFC-2396 (Was: Re: [RT] composition vs. inheritance in blocks)

On Apr 4, 2005 11:16 AM, Daniel Fagerstrom <[EMAIL PROTECTED]> wrote: > Peter Hunsberger wrote: > > >On Apr 4, 2005 10:26 AM, Daniel Fagerstrom <[EMAIL PROTECTED]> wrote: > > > > > >>Pier Fumagalli wrote: > >> > >> > >> > >>>On 31 Mar 2005, at 01:26, Stefano Mazzocchi wrote: > >>> > >>> > > > > >

Re: RFC-2396 (Was: Re: [RT] composition vs. inheritance in blocks)

On 4 Apr 2005, at 16:26, Daniel Fagerstrom wrote: Pier Fumagalli wrote: On 31 Mar 2005, at 01:26, Stefano Mazzocchi wrote: block:super://blah.xml A very simple remark, I don't want to criticise... I'm already slightly "upset" about the "cocoon://" protocol, as it does not follow the URI RFC prop

Re: RFC-2396 (Was: Re: [RT] composition vs. inheritance in blocks)

Peter Hunsberger wrote: On Apr 4, 2005 10:26 AM, Daniel Fagerstrom <[EMAIL PROTECTED]> wrote: Pier Fumagalli wrote: On 31 Mar 2005, at 01:26, Stefano Mazzocchi wrote: As all URI discussions tend to provoke strong feelings for Stefano, it's best to say directly that this question

Re: RFC-2396 (Was: Re: [RT] composition vs. inheritance in blocks)

On Apr 4, 2005 10:26 AM, Daniel Fagerstrom <[EMAIL PROTECTED]> wrote: > Pier Fumagalli wrote: > > > On 31 Mar 2005, at 01:26, Stefano Mazzocchi wrote: > > As all URI discussions tend to provoke strong feelings for Stefano, it's > best to say directly that this question is not important enough

Re: RFC-2396 (Was: Re: [RT] composition vs. inheritance in blocks)

Pier Fumagalli wrote: On 31 Mar 2005, at 01:26, Stefano Mazzocchi wrote: block:super://blah.xml A very simple remark, I don't want to criticise... I'm already slightly "upset" about the "cocoon://" protocol, as it does not follow the URI RFC properly, I'd like to address the problem as early as

Re: [RT] composition vs. inheritance in blocks

On Apr 4, 2005 8:49 AM, Daniel Fagerstrom <[EMAIL PROTECTED]> wrote: > This means IMO that we have to spend time discussing things even if it > in the short time horizont and for ones own goals whould have seemed > more productive to just commit some code. Ultimately, with an Open Source commun

Re: [RT] composition vs. inheritance in blocks

Reinhard Poetz wrote: Stefano Mazzocchi wrote: Thank you. [boy this was exhausting] yes it was and maybe more dicussions will follow. As both Stefano and I are involved in real blocks it seem unavoidable ;) Although a friendlier discussion probably had been more efficient, we actually produced a

Re: [RT] composition vs. inheritance in blocks

Stefano Mazzocchi wrote: Thank you. [boy this was exhausting] yes it was and maybe more dicussions will follow. Daniel, some others and I are putting a lot of energy into making real blocks reality and its important that we _all_ follow the same vision (in the end). Berin summarized (http://www.

DO NOT REPLY [Bug 34283] New: - Tutorial: Write a Custom Generator

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: What is the community looking for?

> 2. Information about cocoon developers. Let's create people pages, > showing who has done what, indicating expertise, links to blogs etc. At > the moment we have the personal pages on the Wiki. I'll start with those. > 3. Errors. Perhaps we could create a hotline, where (in connection with > the

Re: What is the community looking for?

Mark Leicester wrote: Hi everyone, I'm attempting to analyse what the Cocoon community wants from itself. Examining the referrer logs for PlanetCocoon (last week of March) yielded the following top 30 search terms: Mark, I certainly value your effort, but what is PlanetCocoon? What are these fo

Re: What is the community looking for?

I also meant to ask: What is the status of the samples at http://www.cocooncenter.de/, http://www.cocooncenter.org/ ? Mark On 4 Apr 2005, at 08:19, Reinhard Poetz wrote: Mark Leicester wrote: 1. Cocoon Forms examples. I am going to add more recipes on PlanetCocoon, and port the samples to docume

Re: What is the community looking for?

Hi Reinhard, Whatever we come up with will be donated back to the official documentation! Regards, Mark On 4 Apr 2005, at 08:19, Reinhard Poetz wrote: Mark Leicester wrote: 1. Cocoon Forms examples. I am going to add more recipes on PlanetCocoon, and port the samples to documents. Is there anyon

Re: What is the community looking for?

Mark Leicester wrote: 1. Cocoon Forms examples. I am going to add more recipes on PlanetCocoon, and port the samples to documents. Is there anyone else working on this? As some others pointed out on the users list, please consider contributing these docs to the official Cocoon documentation. Wri