Microsoft .NET BCL is quite inextensible.
Yesterday I had to change the data gateway for the xLim communications. “XPO with caching + WebServices + FormsAuth + Medium Trust” didn’t have great performance. So we were pushed towards “XPO with Caching + Full Trust + IIS hosted Binary Remoting + FormsAuth“.
Guess what? Microsoft does not have IIS hosted binary remoting that can work with Forms Authentication. You are supposed to use IIS protection and encryption instead (SSL, windows auth etc).
Well, shared site hosting plan for the current xLim implementation does not support these features (plus we already have Forms Auth security for the Web UI). So, in order to make HttpChannel deliver that cookie through to the Forms Auth, I had to waste a day rewriting the implementation by Microsoft.
If they had a couple of “protected” and “virtual” members in the right places, this would’ve required only 20 LOC modification.
No comments yet.
Leave a comment
Search
Archives
Recent Comments
- aCoder on Extension methods for interfaces
- Requirements for the Photon .NET project | Rinat Abdullin on IRepository, cross-cutting concerns and flexibility
- Nicholas Blumhardt on Extension methods for interfaces
- aCoder on IRepository, cross-cutting concerns and flexibility
- Rinat Abdullin on Blog upgraded
- Rinat Abdullin on Extension methods for interfaces
- IRepository, cross-cutting concerns and flexibility | Rinat Abdullin on Extension methods for interfaces
- Bill Pierce on Blog upgraded
- aCoder on Extension methods for interfaces