Is HTML extension right?

[Howard Lewis Ship <hl...@gmail.com>]

I've been thinking again about the extension for Tapestry templates.

Although T5 again finds the deepest rut in plain old HTML (or XHTML),
I'm sure that SVG or various other markup-related formats are
possible. Possibly a Tapestry page could even be a dynamic CSS file.

So I've been thinking that the template files should get away from a
".html" extension and settle on something Tapestry specific (rather
than content specific), such as ".t", ".tt", ".tsp" (Tapestry Server
Page :-) ), ".tap", etc.

The other question concerns recognizing render requests in URLs.

Render requests look like:

http://...//folder/Page.html
or
http://..//folder/Page.html/context0/context1/context2

The folder/ part is optonal (and may be a number of folders).

The context values are related to the page's passivate and activate
requests (the thematic follow on to T4's external service).

Once I implement the case-insensitive class search feature, I may be
able to reduce the render URL to:

http://...//folder/page
http://..//folder/page/context0/context1/context2

Which I kind of like.  In other words, the point where the page name
ends and the context begins will be determined based on the available
set of pages (in folders).

Meanwhile, action URLs are a lot easier. Currently they are:

http://../folder/Page.action/id-path/context

Note that the period becomes an easy way to recognize the end of the
page name and the start of the action name.

In the short term, I'm thinking of changing this to:

http://../folder/Page.id-path.action/context

... and of course, the coming case-insentivity will apply here as well
(at least to the page name portion).

Thoughts?

-- 
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

Re: Is HTML extension right?

[Howard Lewis Ship <hl...@gmail.com>]

Oops.

On 1/24/07, Howard Lewis Ship <hl...@gmail.com> wrote:
> I've been thinking again about the extension for Tapestry templates.
>
> Although T5 again finds the deepest rut in plain old HTML (or XHTML),
> I'm sure that SVG or various other markup-related formats are
> possible. Possibly a Tapestry page could even be a dynamic CSS file.
>
> So I've been thinking that the template files should get away from a
> ".html" extension and settle on something Tapestry specific (rather
> than content specific), such as ".t", ".tt", ".tsp" (Tapestry Server
> Page :-) ), ".tap", etc.
>
> The other question concerns recognizing render requests in URLs.
>
> Render requests look like:
>
> http://...//folder/Page.html
> or
> http://..//folder/Page.html/context0/context1/context2
>
> The folder/ part is optonal (and may be a number of folders).
>
> The context values are related to the page's passivate and activate
> requests (the thematic follow on to T4's external service).
>
> Once I implement the case-insensitive class search feature, I may be
> able to reduce the render URL to:
>
> http://...//folder/page
> http://..//folder/page/context0/context1/context2
>
> Which I kind of like.  In other words, the point where the page name
> ends and the context begins will be determined based on the available
> set of pages (in folders).
>
> Meanwhile, action URLs are a lot easier. Currently they are:
>
> http://../folder/Page.action/id-path/context
>
> Note that the period becomes an easy way to recognize the end of the
> page name and the start of the action name.
>
> In the short term, I'm thinking of changing this to:
>
> http://../folder/Page.id-path.action/context
>
> ... and of course, the coming case-insentivity will apply here as well
> (at least to the page name portion).
>
> Thoughts?
>
> --
> Howard M. Lewis Ship
> TWD Consulting, Inc.
> Independent J2EE / Open-Source Java Consultant
> Creator and PMC Chair, Apache Tapestry
> Creator, Apache HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work.  http://howardlewisship.com
>


-- 
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com