it's pretty easy, but how about saving it into a sqlite or bdb filestore ? you *could* do a lot of proxying and re-writing , but it seems like what you want to accomplish is standardizing the interface to all this documentation. periodically pulling everything out as json/whaetever and then storing would be the easiest ( imho ) way to handle this. you'd be able use a snapshot of the database to build all your mako/ etc templates against, and the last-valid version of each services docs would always be available ( instead of seeing docs go down if one of the services goes offline )
-- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. 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.
