Re: CMS Site Structures
John Punshon <[email protected]>
| Newsgroups | gmane.comp.cms.cms-forum.general |
|---|---|
| Message-ID | <[email protected]> |
> > I suppose at this stage I am more interested in the actual physical > location of the files and functionality. The site is ASP.Net based - I > am just trying to decide whether to go for a single installation on a > single server under IIS or use one server for the public site and one > for the admin tools. Julian, Vignette stores uploaded files in a central area on a dedicated CMS server machine (there is an api call from your .asp or .jsp code to upload the file to this area). A dedicated process on the CMS server machine coordinates the distribution of the uploaded file to the various (one or more) app servers and a dedicated process on the app server writes the file into the web server(s) docroot(s). The advantage of this architecture is that if you need to scale up to multiple app servers and web servers, the support for it is already there. The drawback is there is a lot of configuration and it only works if you get all the network file system permissions right. John P. http://www.punshon.net