| Stefan [MSFT] 2006-04-27, 1:22 pm |
| Hi James,
your second approach (with the internal and external box) is the usually
used implementation.
Form a security perspective it is much better than placing a read-write box
outside your firewall.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------
"James Doughty" <dont@email.com> wrote in message
news:Xns97B2538C2313Adontemailcom@207.46.248.16...
>I was wondering if the following would be a good design/process flow or
> if it would even work.
>
> We have a CMS box that we will eventually move to the outside of our
> network.
> I was considering the idea of having an ouside box and also having a
> inside box, with both being hooked into the same CMS database. Basically,
> I'd like to make it so that noone could make changes to the CMS system
> unless their on our network and of course at that point and time I can
> assign whatever rights I need to.
> I would have the same templates, webapp, ect on both box and keep them
> syncronized.
>
> Thanks,
> James Doughty
|