You could always consider making publishing a batch process of some sort;
the user clicking Publish or Save or whatever adds those nodes the queue,
and a separate process (probably a Windows Service or something) actually
performs the needed actions.
This might be what you meant by "asynchronousl
Best option is to tune the query or database to get it to run faster. If
what you're asking the db to do can't run in under 60 seconds (which I
think is the default timeout), then you probably need to reconsider
doing it while the user is waiting anyways.
--Mark Brackett
-Original Message
Hi,
I wonder what my design options are for the following problem:
1. We have an ASP.NET application that is a CMS. Part of the functionality is
that an update to a section of the page and then consequencelyupdates all
the child nodes and all their child nodes etc.
2. The application u
