Performance doesn't have priority. It's a typical web application with some database queries, some forms with input validation, but no heavy calculations, so even outdated servers could handle hundrets of concurrened requests.
My focus is rather on reusing code. Lets say I have an "applet" to edit contact details. There will be a read-only view and a form to edit with some input validation. This sub-application shall be reused in different contexts. For example an administrator would use it through the URL /customer/1234/edit and the container might be part as a tab of a surrounding container where other tabs contain lists of his invoices, login history and such. The enduser would access it through /my-details/edit, being part of a dashboard along with fancy graphs, buttons to order new products and whatever. Doing that from scratch would mean, that all of the inhouse routing and view functionality of pyramid would be pretty useless and I would degrade it to a database pool with ORM and manually call renderers. I can't imagine that I'm the first to master this challenge. On Thursday, November 8, 2012 11:30:40 PM UTC+1, Jonathan Vanasco wrote: > > in my opinion there is no best-practice to handle this. it all depends on > how you want to structure the application for ease-of-development vs where > you're willing or unwilling to take performance hits. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-discuss/-/2A_Ru2TKjmQJ. 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/pylons-discuss?hl=en.
