Re: Resuming multicast publishing points
From: Mike M. (nospam_at_someplace.com)
Date: 12/21/04
- Next message: -DC-: "Re: Resuming multicast publishing points"
- Previous message: -DC-: "Resuming multicast publishing points"
- In reply to: -DC-: "Resuming multicast publishing points"
- Next in thread: -DC-: "Re: Resuming multicast publishing points"
- Reply: -DC-: "Re: Resuming multicast publishing points"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 21 Dec 2004 17:14:53 -0500
You could write a program using the SDK that monitors the stream status and
attempts to start it if it is stopped. There is some information in MSDN
with example code on getting the status of a publishing point.
"-DC-" <DC@discussions.microsoft.com> wrote in message
news:47311D7A-EF02-4A1F-9C1F-C2E10068D8CA@microsoft.com...
> I found out today that if you create a multicast publishing point, start
it,
> then disconnect the network cable (simulated hardware failure), the
> publishing point eventually stops. The problem is that when the network
> cable is plugged back in, the publishing point does not automatically
> start/resume. It has to be manually restarted.
>
> Is there some way to get it to automatically restart or, better yet, never
> stop?
- Next message: -DC-: "Re: Resuming multicast publishing points"
- Previous message: -DC-: "Resuming multicast publishing points"
- In reply to: -DC-: "Resuming multicast publishing points"
- Next in thread: -DC-: "Re: Resuming multicast publishing points"
- Reply: -DC-: "Re: Resuming multicast publishing points"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|