Howdy. >From my googling, I'm gathering this is a tall order (due to the servlet spec), but thought I'd ping the list to see if smarter brains than my own had an idea. The idea is that I have particular URL with strict latency requirements that I'd like to run in the same servlet container as my lift app. I have, for the time being, written this as a raw servlet and routed it accordingly in my web.xml. Though this passed through the LiftFilter in 0.9, the performance hit was within reason. I tried to research how to entirely bypass a filter, but the consensus was that if the URLs matched up, I'm out of luck. That's okay.
I've switched over to the 0.10-SNAPSHOT, and it appears that hitting my servlet resource is now generating a 404. I've done some digging in the source, but haven't found much. So, the open question: Am I way off base? Should I just serve my Lift app under a prefix other than / ? I do like clean URLs. Is there a way to have a servlet bypass or be directly routed by the LiftFilter, even if there's an instantiation overhead of the framework? Thanks, -Mark --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
