Nice idea of aggragating couple of similar purpose tweens into one (I'm thinking for example setting HTTP headers).
Anyway the main idea of *seth* is to allow users to quickly create restful apis for small or medium apps. It comes / will come as I finish next release with; - custom paginator - filtering utility - versioning utility - generics and mexins for restful views - command utility (similar to django's manage.py) - exporting utility on top of that - service layer for models, couple of renderers, uploader and some helpers. It may seem to much but my aim is to follow pyramid's philosophy of making code extensible. Unfortunately, couple of components require external libraries (for example sqlalchemy). If someone is interested, I'm in the middle of planning next developing phase so please take a look at examples / tests to get familiar with api and let me know what you think. Cheers, Jacek On Thursday, April 16, 2015 at 11:01:35 PM UTC+2, Jonathan Vanasco wrote: > > Some of the tweens look really useful to me ( the secure and mobile ones > seem like a smart use of tweens!) > > I'm not sure how popular the other ones would/should be -- or how often > people would want to use multiple tweens. > > I'm bringing this up, because if multiple tweens would be used, it might > make sense to consolidate them all into a single tween. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
