Asynchronous server processes via DCOM


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 2 of 2

Thread: Asynchronous server processes via DCOM

  1. #1
    Phil Rylett Guest

    Asynchronous server processes via DCOM


    From a client machine, I wanted to spawn a long running asynchronous process
    on a server. The only way I have come close to doing this truly asynchronously
    is by my client starting the remote process via DCOM and then running a timer
    on my server side to kick off the process. I have read very little on asynchronous
    processing via DCOM and I am not sure if I am missing something. Is this
    the best way to go? Or is there something I am missing? The books talk
    about remote processing being asynchronous, but without the timer strategy,
    my client waits for the remote process to finish. I am using WithEvents
    to communicate status between server and client (and the opportunity for
    the client to send a cancellation message). I did say "come close to doing
    this" as my client machine freezes once the remote call is made. Are there
    any known "gotchas"?
    In the end, I had to disconnect the client from the server and have the server
    process continually polling a run flag in a table which is manipulated by
    the client. This is far from ideal and would appreciate any advice or direction.
    Thank you.
    Share on Google+

  2. #2
    Deborah Kurata Guest

    Re: Asynchronous server processes via DCOM

    Two things to look at:

    1) Maybe message queue could do something for you here
    2) COM+ has a new event mechanism that you may want to take a look at.

    Good luck!
    Deborah

    Phil Rylett wrote in message <38ff20bc$1@news.devx.com>...
    >
    >From a client machine, I wanted to spawn a long running asynchronous

    process
    >on a server. The only way I have come close to doing this truly

    asynchronously
    >is by my client starting the remote process via DCOM and then running a

    timer
    >on my server side to kick off the process. I have read very little on

    asynchronous
    >processing via DCOM and I am not sure if I am missing something. Is this
    >the best way to go? Or is there something I am missing? The books talk
    >about remote processing being asynchronous, but without the timer strategy,
    >my client waits for the remote process to finish. I am using WithEvents
    >to communicate status between server and client (and the opportunity for
    >the client to send a cancellation message). I did say "come close to doing
    >this" as my client machine freezes once the remote call is made. Are there
    >any known "gotchas"?
    >In the end, I had to disconnect the client from the server and have the

    server
    >process continually polling a run flag in a table which is manipulated by
    >the client. This is far from ideal and would appreciate any advice or

    direction.
    >Thank you.



    Share on Google+

Similar Threads

  1. Choose DCOM server
    By Dasensa Esente in forum Enterprise
    Replies: 0
    Last Post: 06-03-2002, 06:05 AM
  2. Replies: 1
    Last Post: 04-16-2002, 06:31 PM
  3. How to authenticate users from a DCOM ActiveX Server
    By Pep Gómez in forum Enterprise
    Replies: 0
    Last Post: 12-20-2000, 11:32 AM
  4. Automated Installation of DCOM Server
    By Manu in forum VB Classic
    Replies: 0
    Last Post: 10-13-2000, 03:28 PM
  5. Making Changes in DCOM Server after Deployment
    By Param in forum VB Classic
    Replies: 1
    Last Post: 09-14-2000, 04:05 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center