 | |
Re: Queued, Pooled component startup questions
Dotnet Framework (Component Services) microsoft.public.dotnet.framework.component_services
 |
| | Thread Tools | Search this Thread | Display Modes |
#1
 
| |||
| |||
|
Re: Queued, Pooled component startup questions -
07-18-2003
, 01:00 PM
|
QC applications don't get started automatically when a client instantiates an instance of a component. This is by design. The whole reason for using QC is because you want to use components in an application that my not be running or that only run every now and then. The method calls on your components will get queued up either on the client or the server and then sit around and wait for you to start the application. Once you start it, the method calls will be processed. If your server application needs to always be running and needs to always process calls as they are made by clients then you probably don't need to use QC. Please see: http://msdn.microsoft.com/library/de...nents_8v6v.asp For more information. Mike "Dave Stienessen" <daves (AT) xata (DOT) com> wrote in message news:uKYRMyHTDHA.3188 (AT) tk2msftngp13 (DOT) phx.gbl... Hi all - I created a Queued, pooled component and the question I have is how to "start" the com+ app automatically - it seems since its queued, the application does not process the queued calls until it is started - This creates deployment issues for me - I can install it and start it with a script, but what about reboots - am I missing something simple? If the solution is to run it as a Windows Service, that's fine, but doesn't that have some impact on what you can do from a queueing and pooling perspective? Thanks Dave |
|
« Previous Thread
|
Next Thread »
| Thread Tools | Search this Thread |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.