I was having to evil AxKit thoughts today. :-) For the day job, I've been looking into the whole [ASP].NET thing. All in all, it has some good qualities in the area of OOP programming web page objects, reusable user controls (taglibs), and output caching.
Specifically on the output caching side of things, the output of any server/user controls (taglibs) can be cached by request params, by headers, by browser, etc. Needless to say, this makes things quite a bit faster while still building dynamic web pages. For a little more info about the matter... http://msdn.microsoft.com/library/en-us/dnaspnet/html/asp03282002.asp So, back to my bad thoughts. I'd like to tinker with the idea within AxKit Taglibs. Maybe by inheriting and extending A::A::L::X::TaglibHelper or A::A::X::L::SimpleTaglib so all taglibs built upon it could have attributes like: varybyparam="r;t" varybyheader="Accept-Language" duration="10" or even better, in their own namespace cache:varybyparam="r;t" cache:varybyheader="Accept-Language" cache:duration="10" That way the output of taglibs could be cached and controlled centrally, without each tablib having to worry about the implimentation details. I'm sure somehow someway, this is possible. Honestly though, after a brief look at the Taglibhelper source, I wouldn't know where to begin. So, here I am, begging for a few words of wisdom, encouragement, verbal abuse, or whatever else comes out of this post. :-) Thanks, -=Chris -- Six of one, 1,426/2,852 dozen of the other. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
