The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Tim Holloway wrote:I may have to ponder that for a while. I'm not sure I have all my facts straight.
If you use a Realm, that means that you shouldn't have written your own login services, and, for that matter, it's fairly unlikely you should have needed a servlet filter. Managing the login process in a Realm is done by Tomcat itself, not your app, regardles of what type of Realm it is - JAAS, JDBC, or even Memory (XML file). And, conversely, Tomcat isn't going to prompt for security credentials when it knows you're already logged in, even if the resource being requested is itself pointed to by an external server.
The exception to this would be if you had 2 separate apps - one to generate the initial google KML reference and one to provide the KLML that the google-served KML referenced. But even that exception would only apply if the 2 apps weren't sharing a single sigon-on Realm.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Consider Paul's rocket mass heater. |