You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Pier Fumagalli <pi...@betaversion.org> on 2004/03/31 12:35:23 UTC
Kernel...
The kernel is now all in CVS (it's still sucky, but I'm still working
on it, at least now it compiles and - seems - to run nicely).
I have a few blocks that I want to develop around it (generic stuff,
JDBC connection pool, poolable factories and event handling). I've
noticed that in the Cocoon 2.2 tree there is no "/src/blocks" directory
structure, can I put them in there?
Pier
Re: Kernel...
Posted by Stefano Mazzocchi <st...@apache.org>.
Pier Fumagalli wrote:
> On 31 Mar 2004, at 17:31, Stefano Mazzocchi wrote:
>
>> Carsten Ziegeler wrote:
>>
>>> I would say: yes, add the blocks directory. It would be good if the
>>> blocks
>>> you add there are not already used in the cocoon-2.1 cvs, which means
>>> just
>>> use unused names.
>>
>>
>> eheh, this is not a problem anymore since these blocks are real ones
>> and they will identified by a URI ;-)
>
>
> To get back to the problem of URL/Namespace/identifier, I just thought
> that for namespace (yes) we can use http://apache.org/cocoon/... since a
> namespace doesn't have to provide any actual data (can return a 404, or
> even a IOException).
try clicking on "http://www.w3.org/1999/xhtml"
> For blocks, though, do we want to have them to point at something (like
> the block descriptor, or the home page) or shall we ignore for now?
we *MUST* be able to serve stuff from our URI block identifiers from the
future. it's actually the whole point in having http: based identifiers.
I think that blocks URI should be starting with
http://cocoon.apache.org/block/ because that doesn't change and also
signifies that these URI don't represent namespaces (which will be still
http://apache.org/cocoon) and will also make it easier for us to control
that URL space when we'll need to publish the metadata in it.
--
Stefano.
Re: Kernel...
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 31 Mar 2004, at 17:31, Stefano Mazzocchi wrote:
> Carsten Ziegeler wrote:
>
>> I would say: yes, add the blocks directory. It would be good if the
>> blocks
>> you add there are not already used in the cocoon-2.1 cvs, which means
>> just
>> use unused names.
>
> eheh, this is not a problem anymore since these blocks are real ones
> and they will identified by a URI ;-)
To get back to the problem of URL/Namespace/identifier, I just thought
that for namespace (yes) we can use http://apache.org/cocoon/... since
a namespace doesn't have to provide any actual data (can return a 404,
or even a IOException).
For blocks, though, do we want to have them to point at something (like
the block descriptor, or the home page) or shall we ignore for now?
Pier
Re: Kernel...
Posted by Stefano Mazzocchi <st...@apache.org>.
Carsten Ziegeler wrote:
> I would say: yes, add the blocks directory. It would be good if the blocks
> you add there are not already used in the cocoon-2.1 cvs, which means just
> use unused names.
eheh, this is not a problem anymore since these blocks are real ones and
they will identified by a URI ;-)
--
Stefano.
Re: Kernel...
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 31 Mar 2004, at 14:26, Carsten Ziegeler wrote:
> Just one addition, we use in Cocoon namespaces a la
> "apache.org/cocoon",
> so the directory structure should look like this I think:
> /src
> /blocks
> /apache.org
> /cocoon
> /jakarta
+1 :-)
Pier
Re: Kernel...
Posted by Stefano Mazzocchi <st...@apache.org>.
Carsten Ziegeler wrote:
> Just one addition, we use in Cocoon namespaces a la "apache.org/cocoon",
> so the directory structure should look like this I think:
> /src
> /blocks
> /apache.org
> /cocoon
> /jakarta
so why not
/src
/blocks
/org
/apache
/cocoon
/jakarta
?
or
/src
/blocks
/o
/r
/g
/.
/a
...
you get the idea
people, we are getting a little bit out of scope here. It does *NOT*
matter how you store blocks in CVS since you WILL NOT be getting out of
CVS anyway!
--
Stefano.
RE: Kernel...
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Just one addition, we use in Cocoon namespaces a la "apache.org/cocoon",
so the directory structure should look like this I think:
/src
/blocks
/apache.org
/cocoon
/jakarta
Carsten
> -----Original Message-----
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> Sent: Wednesday, March 31, 2004 2:21 PM
> To: dev@cocoon.apache.org
> Subject: RE: Kernel...
>
> Pier Fumagalli wrote:
> >
> > On 31 Mar 2004, at 12:21, Carsten Ziegeler wrote:
> >
> > > I would say: yes, add the blocks directory. It would be
> good if the
> > > blocks you add there are not already used in the cocoon-2.1
> > cvs, which
> > > means just use unused names.
> >
> > Given that any block follows a naming such as
> > http://host/name/version, I would think that to avoid
> complications,
> > we could represent that structure in CVS:
> >
> > /src
> > /blocks
> > /cocoon.apache.org
> > /block_name
> > /jakarta.apache.org (???)
> > /block_name
> > /www.orixo.com (???)
> > /block_name
> >
> > And versions are ignored as CVS already provides versioning.
> >
> +1
>
> > Or would "our" block only be http://cocoon.apache.org/ even if we
> > "wrap" stuff from other people? (I'm thinking about Jakarta Commons
> > DBCP and POOL right now, maybe more stuff in the future)
> >
> Even if it will turn out later that we only have "c.a.o"
> blocks, it's easier to go the more verbose way now and don't
> have to change anything later on if we have others as well.
>
> Carsten
>
>
RE: Kernel...
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Pier Fumagalli wrote:
>
> On 31 Mar 2004, at 12:21, Carsten Ziegeler wrote:
>
> > I would say: yes, add the blocks directory. It would be good if the
> > blocks you add there are not already used in the cocoon-2.1
> cvs, which
> > means just use unused names.
>
> Given that any block follows a naming such as
> http://host/name/version, I would think that to avoid
> complications, we could represent that structure in CVS:
>
> /src
> /blocks
> /cocoon.apache.org
> /block_name
> /jakarta.apache.org (???)
> /block_name
> /www.orixo.com (???)
> /block_name
>
> And versions are ignored as CVS already provides versioning.
>
+1
> Or would "our" block only be http://cocoon.apache.org/ even
> if we "wrap" stuff from other people? (I'm thinking about
> Jakarta Commons DBCP and POOL right now, maybe more stuff in
> the future)
>
Even if it will turn out later that we only have "c.a.o" blocks,
it's easier to go the more verbose way now and don't have to
change anything later on if we have others as well.
Carsten
Re: Kernel...
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 31 Mar 2004, at 12:21, Carsten Ziegeler wrote:
> I would say: yes, add the blocks directory. It would be good if the
> blocks
> you add there are not already used in the cocoon-2.1 cvs, which means
> just
> use unused names.
Given that any block follows a naming such as http://host/name/version,
I would think that to avoid complications, we could represent that
structure in CVS:
/src
/blocks
/cocoon.apache.org
/block_name
/jakarta.apache.org (???)
/block_name
/www.orixo.com (???)
/block_name
And versions are ignored as CVS already provides versioning.
Or would "our" block only be http://cocoon.apache.org/ even if we
"wrap" stuff from other people? (I'm thinking about Jakarta Commons
DBCP and POOL right now, maybe more stuff in the future)
Pier
> Carsten
>
>> -----Original Message-----
>> From: Pier Fumagalli [mailto:pier@betaversion.org]
>> Sent: Wednesday, March 31, 2004 12:35 PM
>> To: dev@cocoon.apache.org
>> Subject: Kernel...
>>
>> The kernel is now all in CVS (it's still sucky, but I'm still
>> working on it, at least now it compiles and - seems - to run nicely).
>>
>> I have a few blocks that I want to develop around it (generic
>> stuff, JDBC connection pool, poolable factories and event
>> handling). I've noticed that in the Cocoon 2.2 tree there is
>> no "/src/blocks" directory structure, can I put them in there?
>>
>> Pier
>>
>
>
RE: Kernel...
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
I would say: yes, add the blocks directory. It would be good if the blocks
you add there are not already used in the cocoon-2.1 cvs, which means just
use unused names.
Carsten
> -----Original Message-----
> From: Pier Fumagalli [mailto:pier@betaversion.org]
> Sent: Wednesday, March 31, 2004 12:35 PM
> To: dev@cocoon.apache.org
> Subject: Kernel...
>
> The kernel is now all in CVS (it's still sucky, but I'm still
> working on it, at least now it compiles and - seems - to run nicely).
>
> I have a few blocks that I want to develop around it (generic
> stuff, JDBC connection pool, poolable factories and event
> handling). I've noticed that in the Cocoon 2.2 tree there is
> no "/src/blocks" directory structure, can I put them in there?
>
> Pier
>