Attempting to maintain the essential state of server interactions

Failure so far, the server (ASP.NET) has a really weird state
mechanism that wikipedia says makes data mining difficult.
May abandon this branch
Reproduced the some of the behaviour observed in the browser.
Structural changes to allow easier header adjustments

I've identified the state syncronization mechanism if not its inner
workings. The browser periodically (~10 seconds) sends a post request
to the server with form data with variable __VIEWSTATE equal to some
encoded information. The wiki article suggest this is GUI state,
which is reasonable considering the request is immediatly sent after
a GUI effect.

Its getting to be 4am, I think I've obsessed over this problem enough
today.
Finished ruby API to PVTA bus tracking website data.
Depends on selenium firefox, code is very ugly, no tests.

TODO:
* Make tests
* Make headless
* Separate REST style XML request code from the ugly stateful
  HTML interactions by class. Lazy invokation on stateful code.
* Mask getData queries with rails database queries.