Hi William, [...]
> Thinking more broadly, should the default really be the > inexact match? And > if so, should there be a way to change the default template mode for a > given Router? This is hard to determine the best default case. It seemed more common to rely on hierarchical routing (partial match) than flat routing (exact match). That would be interesting to other users' feed-back on routing practices. > The best I came up with was subclassing Router, overriding > createRoute, > and putting the setMatchingMode bit in there. However, that > then breaks setDefaultRoute, which is not so good. I've added a "defaultMatchingMode" property to Router and don't call createRoute() anymore for the default route. Checked in SVN trunk! > Also, I'm wondering if the Template mode should be an enum > rather than an int; at first glance it looked to me like the Restlet > library was leaning toward enums for type safety. That could be a good usage, but I'm not sure how easy it would be to add new modes without breaking existing applications. Also, enums add a new node in Javadocs which is slightly annoying, at least to me. Best regards, Jerome
