>And Rick, I do not mean this sacastically in any way
>if your answer is "no". Does your web product get
>around this problem? I ask this because on high
>traffic web sites, this has been an absolute
>problem with ASP\VB Com. Reinstalling the hourly dll
>has become a politcal no-no (programmers vs marketing people).

Yes, Web Connection has a mechanism to work around this. It
has the capability to swap in a new COM object on the fly. The
way it works is that you can specify the location of the
server to update and a location where to copy from. WWWC then
unloads all running server instances and copies in the new
version, then restarts the servers automatically. The process
takes about 5 seconds or so depending on the number of servers
that need to get reloaded.

WWWC also allows shutting down all running servers and 'holding'
requests without shutting down the Web server. So if you have
a number of components to update you can hold your specific
application for a few seconds with the guarantee that all servers
are unlaoded.

You can also run in maintainence mode that guarantees only one
instance of your server is running. This allows you to perform
maintainence operations like reindexing and packing data files
if necessary.

All of these are much more efficient than shutting down the Web
server of course and all of this functionality can be adminstered
through an remote HTML interface.