Special considerations for the webfarm versus a "normal" web server
include:
- A load balancing switch distributes your website requests across all active
nodes via the round-robin method for high availability and support of
high-volume traffic.
- Each node within our shared webfarm serves up website
content from a single NAS server (network attached storage). When content is
updated, all nodes in the webfarm are immediately updated.
- FrontPage extensions
to publishing content are not supported on the shared Webfarm, for .NET based
applications, we provide a ‘session-state’ server
Components:
If your website uses a third party component, be aware
that we do not install custom COM+ components on the webfarm. All components are
required to be .NET based and support ‘xcopy’ deployment. This means that the
webfarm doesn’t support many of the components offered on our shared hosting
plan (listed below) and we will not install any COM+ components on the webfarm.
The webfarm is targeted for those who use classic ASP and ASP.NET based
applications but special consideration needs to be made for Classic ASP sites
because of the lack of COM+ support.
Supported
Webfarm Components:
- ASPNet
- POP3
- RichTextBox
- ASPNetMenu
- ASPNetEmail
- ASPNetPOP3
- RichDataPicker
- IP*Works! v6 .NET Edition
- ISAPI RewriteURL
|
Choose an alternate plan for:
- VeriSign PayFlow Component
- IEWeb Controls
- MobileWeb Controls
- IP*Works!
- ASPEmail
- RichSlider
- IBiz QuickBooks Integrator V3 .Net Edition
- IBiz E-Payment Integrator V2 .Net Edition
- List Nanny
- DbCombo
- ASPMail
- ASPUpload 3.0
- ASPTear
- Classic ASP HexGadget Component
- Microsoft Index Server
|
Session State Management:
We provide a state server that can be used for .NET based applications. To
utilize this shared session state server on the webfarm, all ‘session-based’
settings should be commented out or removed from your web.config file so that
they can inherit the settings that we have set in the machine.config file. For
sites using Classic ASP, please request that we configure your webfarm with
sticky-sessions.