On 6/12/06, Henri Dupre <[EMAIL PROTECTED]> wrote:

I think if you set "org.apache.tapestry.home-page" to "index" in your
.application file, then that should be enough.
http://jakarta.apache.org/tapestry/UsersGuide/configuration.html

Ok. I've already done that :-)

[...]

> This would make something similar to a RedirectFilter forwarding
> instead of redirecting...


Yes that is true. But this should send a 200 when you'll hit '/'. The
forwarding happens inside the servlet container not on the client side.

Yes. As the UrlRewrite does, and as the filter would do.
So I still don't get what your solution gives except for "tuning" many
pages which is not something I am in need of.

We have been working recently too to make our website more search engine
friendly... Do you have references or more information on the url format
search engines like?

A lot can be done but is not always specific to Tapestry.
For example, your webserver shoud be optimised a bit with actualis.com
redirecting (with a 301 and not a 302) to www.actualis.com (the same
could apply to .fr domains). This is important because otherwise
Google thinks is it a two distincts sites, one being a copy of the
other and your ranking can be penalized because of this.

Now, I would like to be able also to have URLs without the '.html'
extension. This has no meaning at all and as explained in
http://www.w3.org/Provider/Style/URI, the extension somehow expose the
technology used and this is something you should avoid. What would
happen if you redesign let's say a PHP website into a Tapestry app?
You would keep your '.php' extension for HTML pages generated by
Tapestry?

I'd like to be able to put pages in "virtual directories" although the
Tapestry pages "model" would be "flat": meaning all templates would be
in the same directory, only a configuration file would indicate that
page XXX should be bound to URL "/whatever-i-want/my-wonderful-page"
for example. Of course this setting would be used by all links
components in order to generate something coherent. Ideally we could
be able to use a url mapping service (hivemind service) which would
allow us to have the mapping in a database instead for example.

I have been also thinking of writing in tapestry a dynamic sitemap for
google. Do you know if this is worth it?


Generating a Google sitemap has not really proved to be useful unless
you have lots of pages, in which case search engines might be a little
bit lost and drop pages. This can be useful too when you have ugly
URLs. Sitemaps only give an indication to Google that you have some
fresh content that should be indexed.


Regards,
Jérôme.


--
Jérôme BERNARD,
Kalixia, SARL.
http://weblog.kalixia.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to