Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am considering pre-loading routes to static content pages, allowing for n-depth nesting of content. I have a solution spiked that provides a bit of comfort in terms of the number of potential routes registered, but I’m wondering if I’m making the system overly complex.
At what number of registered routes do you suspect a basic hosting account would start to suffer in performance? These routes are pure-text, with no need to parse values.
Route-parsing, compared with database access? I would guess the route-parsing is pretty cheap. Until you get into the thousands of routes.