This is highly commendable effort. I have been the lead programmer of an India based travel search engine, so understand the value of this data. Another proble

This is highly commendable effort. I have been the lead programmer of an India based travel search engine, so understand the value of this data. Another problem to be solved is: Building a cache of seat availability. Basically, the Indian Railways guys can not provide the availability fast enough. And it affects every body - from end consumers using their websites, to OTA sites, to travel-search players. I can't understand, why no body in the Railways IT dept. (i.e. CRIS) thought of having a PUSH based cache. The way it can work is each reservation/booking done causes a PUSH onto the state of the seat availability cache. Which is a very fast cache (probably based on memcached). If they allow me, I can code the cache for FREE, for them. Provided they also stop being so possessive about their data. And allow for apps like yours and mine to flourish, which ultimately benefit the traveler. EDIT: minor rephrase