You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Ivelin Ivanov <iv...@apache.org> on 2002/10/13 17:15:10 UTC
[Ann] Documented the Pipeline "expires" parameter
I finally found the time to debug the code and understand how the pipeline
"expires" parameter works.
Although I wanted to use it for a long time, all my requests for
documentation were ignored :\ and I didn't want to once again look behind
the curtain for something that is conceptually very simple.
Oh, well...not the first, nor the last one.
Since I believe this parameter is a very important part of Cocoon's
scalability, I updated the Performance Tips document to explain how and why
this parameter should be used.
There have been quite a few additions to the documentation lately.
When is the next live site update planned to happen?
-=Ivelin=-
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Ann] Documented the Pipeline "expires" parameter
Posted by Ivelin Ivanov <iv...@apache.org>.
AFAIK, 2.1-dev.
----- Original Message -----
From: "Ugo Cei" <u....@cbim.it>
To: <co...@xml.apache.org>
Sent: Monday, October 14, 2002 2:26 AM
Subject: Re: [Ann] Documented the Pipeline "expires" parameter
> Gianugo Rabellino wrote:
> > Ivelin Ivanov wrote:
> >
> >> I finally found the time to debug the code and understand how the
> >> pipeline
> >> "expires" parameter works.
> > Urgh... I feel particularily guilty, being myself the original proposer
> > and author of that component. Unfortunately I'm really short on time
> > lately, and I'm lagging behind the new development. Anyway, I'm
> > constantly monitoring the -dev list but I can't remember of any
> > particular request for documentation on it. I'll try to catch up,
> > meanwhile thanks for covering me up!
>
> Does that component work in 2.1-dev, 2.0.3, 2.0.4-dev? I have a couple
> of applications based on 2.0.3 that might really benefit from it. I can
> upgrade them to 2.0.4-dev but not to 2.1-dev.
>
> Ugo
>
>
> --
> Ugo Cei - http://www.beblogging.com/blog/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Ann] Documented the Pipeline "expires" parameter
Posted by Ugo Cei <u....@cbim.it>.
Gianugo Rabellino wrote:
> Ivelin Ivanov wrote:
>
>> I finally found the time to debug the code and understand how the
>> pipeline
>> "expires" parameter works.
> Urgh... I feel particularily guilty, being myself the original proposer
> and author of that component. Unfortunately I'm really short on time
> lately, and I'm lagging behind the new development. Anyway, I'm
> constantly monitoring the -dev list but I can't remember of any
> particular request for documentation on it. I'll try to catch up,
> meanwhile thanks for covering me up!
Does that component work in 2.1-dev, 2.0.3, 2.0.4-dev? I have a couple
of applications based on 2.0.3 that might really benefit from it. I can
upgrade them to 2.0.4-dev but not to 2.1-dev.
Ugo
--
Ugo Cei - http://www.beblogging.com/blog/
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Ann] Documented the Pipeline "expires" parameter
Posted by Ivelin Ivanov <iv...@apache.org>.
No problem,
I have noticed that the right time to submit documentation is at the time I
submit code. Later I tend to forget and it becomes increasingly difficult to
find time for documenting old code.
Thanks for the code anyway, very useful.
Cheers,
Ivelin
----- Original Message -----
From: "Gianugo Rabellino" <gi...@apache.org>
To: <co...@xml.apache.org>
Cc: <co...@xml.apache.org>
Sent: Sunday, October 13, 2002 2:35 PM
Subject: Re: [Ann] Documented the Pipeline "expires" parameter
> Ivelin Ivanov wrote:
> > I finally found the time to debug the code and understand how the
pipeline
> > "expires" parameter works.
> > Although I wanted to use it for a long time, all my requests for
> > documentation were ignored :\ and I didn't want to once again look
behind
> > the curtain for something that is conceptually very simple.
>
> Urgh... I feel particularily guilty, being myself the original proposer
> and author of that component. Unfortunately I'm really short on time
> lately, and I'm lagging behind the new development. Anyway, I'm
> constantly monitoring the -dev list but I can't remember of any
> particular request for documentation on it. I'll try to catch up,
> meanwhile thanks for covering me up!
>
> Ciao,
>
> --
> Gianugo Rabellino
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Ann] Documented the Pipeline "expires" parameter
Posted by Ivelin Ivanov <iv...@apache.org>.
No problem,
I have noticed that the right time to submit documentation is at the time I
submit code. Later I tend to forget and it becomes increasingly difficult to
find time for documenting old code.
Thanks for the code anyway, very useful.
Cheers,
Ivelin
----- Original Message -----
From: "Gianugo Rabellino" <gi...@apache.org>
To: <co...@xml.apache.org>
Cc: <co...@xml.apache.org>
Sent: Sunday, October 13, 2002 2:35 PM
Subject: Re: [Ann] Documented the Pipeline "expires" parameter
> Ivelin Ivanov wrote:
> > I finally found the time to debug the code and understand how the
pipeline
> > "expires" parameter works.
> > Although I wanted to use it for a long time, all my requests for
> > documentation were ignored :\ and I didn't want to once again look
behind
> > the curtain for something that is conceptually very simple.
>
> Urgh... I feel particularily guilty, being myself the original proposer
> and author of that component. Unfortunately I'm really short on time
> lately, and I'm lagging behind the new development. Anyway, I'm
> constantly monitoring the -dev list but I can't remember of any
> particular request for documentation on it. I'll try to catch up,
> meanwhile thanks for covering me up!
>
> Ciao,
>
> --
> Gianugo Rabellino
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
Re: [Ann] Documented the Pipeline "expires" parameter
Posted by Gianugo Rabellino <gi...@apache.org>.
Ivelin Ivanov wrote:
> I finally found the time to debug the code and understand how the pipeline
> "expires" parameter works.
> Although I wanted to use it for a long time, all my requests for
> documentation were ignored :\ and I didn't want to once again look behind
> the curtain for something that is conceptually very simple.
Urgh... I feel particularily guilty, being myself the original proposer
and author of that component. Unfortunately I'm really short on time
lately, and I'm lagging behind the new development. Anyway, I'm
constantly monitoring the -dev list but I can't remember of any
particular request for documentation on it. I'll try to catch up,
meanwhile thanks for covering me up!
Ciao,
--
Gianugo Rabellino
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [Ann] Documented the Pipeline "expires" parameter
Posted by Gianugo Rabellino <gi...@apache.org>.
Ivelin Ivanov wrote:
> I finally found the time to debug the code and understand how the pipeline
> "expires" parameter works.
> Although I wanted to use it for a long time, all my requests for
> documentation were ignored :\ and I didn't want to once again look behind
> the curtain for something that is conceptually very simple.
Urgh... I feel particularily guilty, being myself the original proposer
and author of that component. Unfortunately I'm really short on time
lately, and I'm lagging behind the new development. Anyway, I'm
constantly monitoring the -dev list but I can't remember of any
particular request for documentation on it. I'll try to catch up,
meanwhile thanks for covering me up!
Ciao,
--
Gianugo Rabellino
Re: [Ann] Documented the Pipeline "expires" parameter
Posted by Ivelin Ivanov <iv...@apache.org>.
Woops. I forgot about the tagging thing.
Since you did it for XMLForm, I will need to learn how to do it now.
----- Original Message -----
From: "Diana Shannon" <sh...@apache.org>
To: <co...@xml.apache.org>
Sent: Monday, October 14, 2002 8:27 AM
Subject: Re: [Ann] Documented the Pipeline "expires" parameter
>
> On Sunday, October 13, 2002, at 11:15 AM, Ivelin Ivanov wrote:
>
> > There have been quite a few additions to the documentation lately.
> >
> > When is the next live site update planned to happen?
>
> I'll update later this week. Ivelin, you can save me considerable time
> by making sure all your cvs doc commits go to *both* HEAD and release
> branches, ok? If the content or doc relates to one cvs version only,
> then simply flag it as such, like "cocoon 2.1 only" etc. like we did for
> your XMLForm How-To.
>
> Thanks.
>
> Diana
>
Re: [Ann] Documented the Pipeline "expires" parameter
Posted by Diana Shannon <sh...@apache.org>.
On Sunday, October 13, 2002, at 11:15 AM, Ivelin Ivanov wrote:
> There have been quite a few additions to the documentation lately.
>
> When is the next live site update planned to happen?
I'll update later this week. Ivelin, you can save me considerable time
by making sure all your cvs doc commits go to *both* HEAD and release
branches, ok? If the content or doc relates to one cvs version only,
then simply flag it as such, like "cocoon 2.1 only" etc. like we did for
your XMLForm How-To.
Thanks.
Diana