> 1. I would imagine that setting up a basic numeric value to indicate > order would be much easier to understand than regular expression patterns.
We want both. I'm emphatic on that point. Regular expressions are a standard pattern matching facility that any reasonably competent deployer ought to know and be comfortable drafting. We've had a number of incidents over the years where the use of Ant patterns has caused a fair bit of confusion and frustration. They're just similar enough to be misleading yet lack the expressive power of a posix regular expression. The use of an explicit order field is both clear and performant. There is no conceivable algorithm for "longest match" that would not require evaluating against _all_ registered services. Compare that to the existing algorithm that short circuits on first match. We have a growing list of services and incurring more processing overhead at the point of granting every ticket is a non-starter. I'm confident the UI issues with the current service manager are just that -- matters of user interface design. I think the ability to sort by arbitrary column would be beneficial, but they should be sorted by order by default. M -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
