M
mallik
http://www.samspublishing.com/articles/article.asp?p=25466
the down-side of the proposed solution in the above article is... those Application_AuthenticateRequest, Application_AuthorizeRequest events will be raised during both the Page_Load() and also during Postbacks.
yes, we can make it faster by caching it... but for a application which has some 200 pages and a 1000 pages... the datastructure(hashtable/stringcollection/hybriddictionary whatever) gets really big and it has some over-head searching thru that data structure...
appreciate any ideas to make these events(in the custom httpmodule) fire only during page_load() not during postbacks()...
Thank you,
the down-side of the proposed solution in the above article is... those Application_AuthenticateRequest, Application_AuthorizeRequest events will be raised during both the Page_Load() and also during Postbacks.
yes, we can make it faster by caching it... but for a application which has some 200 pages and a 1000 pages... the datastructure(hashtable/stringcollection/hybriddictionary whatever) gets really big and it has some over-head searching thru that data structure...
appreciate any ideas to make these events(in the custom httpmodule) fire only during page_load() not during postbacks()...
Thank you,