Thanks for this info. It solves a problem that I've had with restarting the streams I publish using the Smooth Streaming Format SDK.
By simply adding the option to the .isml file and we can now start and stop streams without getting connection errors from the server.
By the way, there is no HTTP responce when re-initiating a stream when the option is NOT set, it just times out. In my implementation, it fails in WinHttpReceiveResponse with ERROR_WINHTTP_CONNECTION_ERROR. This could be a bit more elegant on the server-side
(file not found, whatever). In particular, at the moment, a wire-shark trace of tcp traffic shows a RST bit on the ACK frame from the server on the initial POST opperation -- it will be much easier for everyone to handle a 400-level error when restart is
not enabled, or the pub-point cannot handle a new connection.
The practice of having "hidden" features combined with removal of the command line interface is making it really hard (for me, maybe others too) to implement unattended encoding and publishing systems.
Please improve the documentation of the SDK, especially the integration of Expression Encoder and IIS Media Services 4.1, help us out!
comporder1
41 Posts
Re: Publishing Point auto Restart
Jul 19, 2010 08:26 PM|LINK
I am afraid I must ask.... How do I implement this code? Is it .asp? .php? The last link says I must reference two .dll files. How do I do that?
What I need to be able to do is remotely start/restart a publishing point.
Thank you to anyone who can help me.
Nicolas.Drou...
43 Posts
Re: Publishing Point auto Restart
Jul 23, 2010 04:54 PM|LINK
Hi Jimmy,
Thanks for this info. It solves a problem that I've had with restarting the streams I publish using the Smooth Streaming Format SDK.
By simply adding the option to the .isml file and we can now start and stop streams without getting connection errors from the server.
By the way, there is no HTTP responce when re-initiating a stream when the option is NOT set, it just times out. In my implementation, it fails in WinHttpReceiveResponse with ERROR_WINHTTP_CONNECTION_ERROR. This could be a bit more elegant on the server-side (file not found, whatever). In particular, at the moment, a wire-shark trace of tcp traffic shows a RST bit on the ACK frame from the server on the initial POST opperation -- it will be much easier for everyone to handle a 400-level error when restart is not enabled, or the pub-point cannot handle a new connection.
Thanks again!
Regards,
-Nick
pcpal01
1 Post
Re: Publishing Point auto Restart
Apr 07, 2011 03:13 AM|LINK
How and where to you place this statement?
Nicolas.Drou...
43 Posts
Re: Publishing Point auto Restart
Jun 28, 2011 12:05 PM|LINK
Just to close off the thread:
Edit the .isml file for your publishing point (in notepad) and add the following:
<meta name="restartOnEncoderReconnect" content="true" />
along with the other tags generated via the IIS Media GUI.
ejadib
19 Posts
Re: Publishing Point auto Restart
Jul 01, 2011 02:11 AM|LINK
Hi,
Sam wrote an excellent post describing these hidden and advanced properties:
Hope this helps,
Ez.
http://blogs.southworks.net/ejadib
Live Smooth Streaming Publishing Points
ANDDYYYY
1 Post
Re: Publishing Point auto Restart
Feb 28, 2012 04:24 PM|LINK
The practice of having "hidden" features combined with removal of the command line interface is making it really hard (for me, maybe others too) to implement unattended encoding and publishing systems.
Please improve the documentation of the SDK, especially the integration of Expression Encoder and IIS Media Services 4.1, help us out!