I'm not sure I follow - are you saying we should break out default auth *after* 2.0, and then implement the hint idea, or break out auth before 2.0, then after 2.0 deal with the hints?Sorry, should've been clearer. I meant that we can deal with the hints post-2.0 or whenever possible. But, no problem with breaking out default auth. now.
Just FYI, I've got auth mostly broken out now...Great...I've got the other ones broken out into individual modules, starting to test. Some interesting dependency issues popped up. Default persistent is using the Excalibur cache directly, became evident once I moved out svc-cache-excalibur. For now, I have just put the Excalibur cache JAR directly in svc-persist-default, we can change to use the generic cache "service" later. Also, found DefaultModelRequest was being used directly in a couple places, I think those can be taken care of pretty easily.
Shash
http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
