Aug 012006
 

Last night I discovered a caching bug related to vuxml processing. I fixed it. Today I realized the same issue affects processing of MOVED and UPDATING. Coded both of them today as well. Anyone got a MOVED or UPDATING commit just waiting to happen? ;)

Ideally, I’d be able to find somewhere in the database that I could put a trigger and then launch a cache removal from that.

I’ve been considering the NOTIFY feature available with PostgreSQL. I would create a rule/trigger on the port table and have a listening daemon clear out the cache automagically. Interesting. I may just have to try this out…

Website Pin Facebook Twitter Myspace Friendfeed Technorati del.icio.us Digg Google StumbleUpon Premium Responsive