As a sort of nitpicky aside... does URLRewriterService have to be
called that? (Since we're still in new feature api-change mode,
here... :).
What about just URLRewriter? Or URLRewriteHandler? Either of those
seem to gel a little more with existing naming (plus we then don't
have the redundancy of
org.apache.tapestry5.*services*.URLRewriter*Service* (with * added for
emphasis).
Just a thought...
Robert
On Mar 30, 2009, at 3/3010:52 PM , Thiago H. de Paula Figueiredo wrote:
Robert, nice suggestions. My idea was to add to to add two methods
to URLRewriterRule, boolean rewritesInboundURLs() and
rewritesOutboundURLs() (or any other better name, suggestions
welcome) to URLRewriterRule and then change the internal services
implementation accordingly.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
