Aggie RC4 featured an HTTP cache for the first time. Unfortunately, with this (welcome) addition also came the problem that no protocol other than HTTP now works – or at least that’s how it looks to me. The code simply assumes that HttpWebRequest and HttpWebResponse are delivered from the general WebRequest and WebResponse.

 

This wouldn’t be a problem, except it means that now tricks such my client-side transformations (XSLT and RssDistiller) do not work in Aggie, because they rely on protocol handlers that are not HTTP.

 

We can modify Site.Go() to handle HTTP requests differently, or attempt to modify the cache to work with any protocol (not necessarily HTTP), which seems to be a more forward looking. (I suppose I could also add hacks to make things work in RC5, but I don’t like hacks – they have a way of remaining.)

 

Comments?

 

Ziv Caspi

  cell: +972-53-668-751

    web: http://radio.weblogs.com/0106548/