Re: ASP.NET/IIS6 Web Farms - confused

Tech-Archive recommends: Fix windows errors by optimizing your registry

The "shared dll" part is easy to accomplish.
Just install your common assembly to the machine's GAC.

Re shared variables, your best bet is storing them in a database,
where they can be accessed by anybody you want to allow access to.

re:
> there must be a payload with using a database rather than memory.

You could always have the original data in the database,
so that only the initial hit will generate a payload,
and use the Cache object to store your data in memory.

Using a SQL Cache dependency will allow you
to re-hit the database if the data has changed.





Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================

<postings@xxxxxxxxxxxxxxx> wrote in message
news:1121784016.396220.262230@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi
>
> I was under the mistaken impression that Application variables could be
> shared by websites running under the same IIS process. Looking at the
> documentation this isn't true.
>
> So what is the best way to share services/pages/code between IIS6 and a
> multitude of websites under a web farm? The only thing I could think of
> is that XML web services could help here, but is that it?
>
> I have dabbled a little with SQL Server and saving session state, but
> I'd rather avoid having the session's conflict with each other
> (that's why I mistakenly thought the application variable could be
> useful in this instance, it was separate to the session state), and
> there must be a payload with using a database rather than memory.
>
> Can anybody give me any pointers on what ASP.NET technologies I should
> be looking at when coding/designing web farms? What really interests me
> is websites being able to access one common dll and be able to exchange
> variables with each other. I could have a master website where
> code/variable could be utilized in this instance.
>
> Many Thanks!
>
> Alex


.

Quantcast