On the master server, make sure that stream splitting is enabled for
each publishing point.
Select the publishing point, go to the properties tab, then general.
First option is stream splitting. Right click and select 'enable'
You can limit the number of distribution streams in the 'limits'
section
TotalStream.net
frankb - 25 Aug 2008 08:12 GMT
Thanks for the reply, but I don't think this is our problem.
Just to make sure, this is what we are working with:
First we have one origin server for the content provider. On this
server there is a broadcast publishing point which has stream
splitting enabled.
Second, we have one master cache server which has a cacheproxy plug-in
installed and acts as a reverse proxy.
Third, we have several edge cache servers. These have the same
cacheproxy plug-in installed and act as reverse proxy also.
The desired behavior is:
A media player is connecting to an edge cache. This one is using one
connection to stream the data from the master cache. The master cache
is using only one connection to stream from the content provider
server. If another player is connecting to another edge cache, there
will be only one more connection to the master cache. The connection
to the content provider is reused.
What we see is that if a second edge cache is connecting to the master
cache a new connection to the content provider is made :(
The confusing thing is, we are using the same software (the plug-in)
on both the master and the edge cache.
Inside the plug-in we are using the minimum code path. In
IWMSCacheProxy.QueryCache we just do some sanity checks and if it is
not available we get the content information. We just call
IWMSCacheProxyCallback.OnQueryCache with
WMS_CACHE_QUERY_HIT_PLAY_BROADCAST as response.
What’s more confusing, if we are using some media players to connect
directly to the master cache the stream splitting is working as
expected!
So maybe you or somebody else can enlighten me about the reason.
Thanks in advance