COM+ Event puzzle



Hi, all,

I am going to utilize COM+ Event to make an application to track the
database modification, if someone upated the database, then the COM server
would publish a method to all the subscribed clients to refresh the dataset.
But if there were one or more clients were in deadlock, the server might
keep on publishing, then comes the question:

1. Supposed that computer A were in deadlock and there were 3 refreshing
command published, after it works properly again, would it execute the
outdated THREE refreshing command one by one?

2. If there were some clients in deadlock, would it be any bad impact on
those other clients or server?

Thanks a lot.

Jak


.



Relevant Pages

  • Re: COM+ Event puzzle
    ... >> But if there were one or more clients were in deadlock, the server might ... Supposed that computer A were in deadlock and there were 3 ... >> outdated THREE refreshing command one by one? ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: Double streams
    ... So a deadlock of some sort i would guess. ... So two clients, each of whom has the Foo* Streams, and inside these there is a Remote interface, which can call readand write, respectively, on an object on the server. ...
    (comp.lang.java)
  • Re: COM+ Event puzzle
    ... would publish a method to all the subscribed clients to refresh the dataset. ... But if there were one or more clients were in deadlock, the server might ... Supposed that computer A were in deadlock and there were 3 refreshing ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: COM+ Event puzzle
    ... But if there were one or more clients were in deadlock, the server might ... outdated THREE refreshing command one by one? ...
    (microsoft.public.dotnet.distributed_apps)
  • RE: Users Cant Access Documents on Server
    ... Thanks for using the SBS newsgroup. ... As well as we know, if a workstation would not access network shares, then ... Leave the Default Gateway of the internal NIC blank of the server box. ... Clients That Require SMB Signing ...
    (microsoft.public.windows.server.sbs)