On Friday, July 24, 2015 at 2:06:15 PM UTC-4, Richard Kuesters wrote: > > well, application-wise it is really to run other procedures, not from the > database or python side, but from a message broker that's expecting > anything to happen to that value -- even if it's just a touch :) > > err ... it's quite a specific architecture for dumb clients, so i'm just > taking some extra security measures ;) >
It's not really that dump of an architecture. I picked up on the value/importance of a simple touch. Just throwing out some more ideas... We have a caching system in place for public data for a pyramid app using SqlAlchemy and Dogpile(redis). When objects are fetched form the cache, a `postcache` hook is performed and... if the object requires a lot of processing... it can register the object and an action into a global pool. We then use an event in Pyramid to pop and process everything in the pool. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
