Re: Allow/restrict IPs
- From: "Vladimir Polischuk" <vlad@xxxxxxxxxxxxxxxxx>
- Date: Mon, 19 May 2008 12:24:24 +0300
Yes, I think you need to go the other way - use Windows Media Services for
the access control. Let me know if you need more details.
Vladimir V. Polischuk
www.voynex.com - custom software development,
solutions for Windows Media (pay-per-minute billing,
streaming content protection, access control)
"Jere cro" <jerislav@xxxxxxxxx> wrote in message
news:a57cfc40-a95a-42b4-ad58-fcc0bf9e93af@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Apr 28, 10:20 pm, shil <shil...@xxxxxxxxx> wrote:
Thanks Chris for the reply. We are using C#.net for our development.
Do you know any API equivalent to IWMAddressAccess in C#.net which we
can use?
According to documentation, it is not possible to control client
connections trough WMEnc SDK.
(From MSDN)
You can also restrict which clients have access to the host computer
by applying an IP address mask to connecting clients. By default, any
client up to the connection limit is allowed. Although the Windows
Media Encoder SDK does not include an API to do this, you can use the
Windows Media Format SDK. For more information, see the
IWMAddressAccess and IWMAddressAccess2 interfaces in the Windows Media
Format SDK Help.
.
- Follow-Ups:
- Re: Allow/restrict IPs
- From: Jere cro
- Re: Allow/restrict IPs
- References:
- Re: Allow/restrict IPs
- From: Jere cro
- Re: Allow/restrict IPs
- Prev by Date: WMP11 UserLastPlayedTime attribute readonly?
- Next by Date: First frame as keyframe - writing compressed samples
- Previous by thread: Re: Allow/restrict IPs
- Next by thread: Re: Allow/restrict IPs
- Index(es):
Relevant Pages
|
Loading