Hi Robert,
Good point on the caching, I almost forgot about it.
Unfortunately I can't really do the separation in app.yaml because the
path overlap between the backend and frontend. Thinking about using
the URL prefix (e.g. 'www' vs 'service') to dispatch differently.
What's your thoughts?
Hey Mars,
Personally, I'd say do what ever makes your code the most readable
and maintainable and the app the most user-friendly. I suspect
Rodrigo is right, you'd need quite a few rules before you'll get a
noticeable performance impact.
Robert
On Wed, May 4, 2011 at 17:52, Mars
I guess even with 10 thousand rules it would be very fast and
building/matching would take milliseconds. Easy to test it yourself.
-- rodrigo
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to
On Tue, May 3, 2011 at 5:29 PM, Rodrigo Moraes rodrigo.mor...@gmail.com wrote:
I guess even with 10 thousand rules it would be very fast and
building/matching would take milliseconds.
There's a limit to the number of handlers you can define in app.yaml.
IIRC, it's about 100.
--
You received
Good point Robert. In fact this is exactly what I'm pondering now.
I have two apps, one for backend and one for frontend. I like the
clean cut but the extra network latency between the two introduces
100~200ms delay for my page load. Want to combine the two together but
doesn't want to lose the
Hey Mars,
If you define the application at the modules level (ie outside of
main) it will be cached between requests. So even if it does add a
little overhead due to more rules, it probably won't matter much
across requests. If you want your stuff isolated, just use two
mappings in app.yaml.
There's a limit to the number of handlers you can define in app.yaml.
IIRC, it's about 100.
Oh, I was only referring to matching URLs passed to webapp.WSGIApplication
(Python).
I'd just say you don't need to worry about that. You need *a lot* of URL
patterns for the matching process to be
