[Mono-devel-list] using xsp as webserver

eric lindvall eric at 5stops.com
Tue Jul 8 14:27:59 EDT 2003


the problem with this is that the System.Web.Caching namespace is not
accessable from corlib.

e.


On Tue, 08 Jul 2003, Tomasz.Kaszuba at inteligo.pl wrote:

> Actually I believe that MS uses the Cache and the CacheDependency class. You
> can set up your Cache class to be dependent on a file on the disk. (which in
> this case is the web.config file) If the file changes the Cache class
> automatically updates itself and notifies all the attached listeners that
> it's changing. 
> 
> In my opinion, this is where I think the caching should take place.
> 
> -----Original Message-----
> From: Ivan Hawkes [mailto:blackhawk at ivanhawkes.com] 
> Sent: Tuesday, July 08, 2003 9:15 AM
> To: Jerome Laban
> Cc: mono-devel-list at lists.ximian.com
> Subject: Re: [Mono-devel-list] using xsp as webserver
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Jerome Laban wrote:
> 
> | Agreed, that patch was like a "proof of concept" :) Right now I don't
> | think one would modify configuration file as the server is running, at
> | least it could be told not to do it.
> | I'll try to look at doing the caching in the config classes, if noone is
> | already on it.
> |
> | Doing some quick profiling showed that these files a read a *lot* of
> | time, this would benefit a broader set of classes that rely on this.
> |
> | Jerome.
> 
> This is what MS do I believe. The config file is loaded at startup and
> cached from there. If you make a change to Web.config it needs to
> recompile the application (or maybe just that directory) before it can
> continue running.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iQIVAwUBPwpvY/r1e7bH1pzBAQJ0Sg//b9p/2r5sVZwWWmxSjlOWsM3pzzL4dTSh
> JqyMuFw7tClOHUexnTY9PPbUIb5T5vDcW6zeR5OR4ppwG78Y38YR1sp/HvYrZEtn
> 0DdQHkCtmAmQlwfw6VvxiPCUsGD3IJ8d3VSMGQMCOuogNP3tVbow/byVoLtVKjzB
> MVa497OMxiEM+/v/RPJKUV7qoKM2t9UVHRpI0GKl5m8SQX+Q7oja1kjpE+jXJHLZ
> xIn27+GkxoQmyVoOYQUtbFIHoK+DcVu9RFu2z856N3g1SE93ZmbO8V3desiqZ3C0
> WRAidiHMb9/EuXNIcNali67V8jVyNECMXXk7uiOOChOKfa0pU3pQfbxyQcQAIc8t
> ccs0ZKwEWzFSihFdxGpd9iLcWSFKU6W7/iS/jAptRhwcFJUKcpujh+6jvfpQeKq6
> lXtuuL0a2pHMhlxzk4tQ0EfmTcPiD1rrN+z0pKpRZOhLguuovtRq8pBKD2cC2MPA
> 5kDgHQcjcitV83+egfgtF8gEZKbyWoR9doTbBO1DRr1qRhGlafitVtIafxx02vtX
> bRioc6B2ldL9iHIDdIc3G+FeL7AnuNeaiVvabbYt62o+SEj2ANnw2Dmy3QcVDc/A
> KU0hZTLvJ+MW0IheBxSOcIGwayCv9DPg8K5c1uWG08bGPiqqpYUOsfcucpExLwlY
> ouQu42Bmj7o=
> =0nxG
> -----END PGP SIGNATURE-----
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> 
> 
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list



More information about the Mono-devel-list mailing list