Hi
Am Samstag, 13. November 2010 schrieb Steffen Barszus:
> On Fri, 12 Nov 2010 23:10:23 +0100
>
> Dieter Hametner wrote:
> > The live-plugin has support (contributed by third party developer)
> > for SSL connections to its internal web-server. See the README file
> > in LIVE for more details.
>
Hi
Am Samstag, 13. November 2010 schrieb Christian Tramnitz:
> Am 13.11.2010 11:23, schrieb Klaus Schmidinger:
> > However, my suggestion would be to implement authentication, encryption
> > and compression as an externel "layer". Much like a proxy, which offers
> > [...]
> I tend to agree with Di
On Fri, 12 Nov 2010 23:10:23 +0100
Dieter Hametner wrote:
> The live-plugin has support (contributed by third party developer)
> for SSL connections to its internal web-server. See the README file
> in LIVE for more details.
>
> The concept how LIVE works as plugin could be generalized to provide
Am 13.11.2010 11:23, schrieb Klaus Schmidinger:
However, my suggestion would be to implement authentication, encryption
and compression as an externel "layer". Much like a proxy, which offers
a secure port to the outside world, and internally connects to the
standard SVDRP interface of VDR. That
On 12.11.2010 23:10, Dieter Hametner wrote:
> Hi
>
> Am Freitag, 12. November 2010 schrieb Christian Tramnitz:
>> Right now when the needs of a vdr extension goes beyond core SVDRP
>> capabilities a different approach is being used by the each extensions.
>> Prominent examples are:
>> - vdradmin (
Hi
Am Freitag, 12. November 2010 schrieb Christian Tramnitz:
> Right now when the needs of a vdr extension goes beyond core SVDRP
> capabilities a different approach is being used by the each extensions.
> Prominent examples are:
> - vdradmin (using native SVDRP and suffering from its performance,
On 12.11.2010 17:04, Christian Tramnitz wrote:
> Right now when the needs of a vdr extension goes beyond core SVDRP
> capabilities a different approach is being used by the each extensions.
> Prominent examples are:
> - vdradmin (using native SVDRP and suffering from its performance,
> optional use
Right now when the needs of a vdr extension goes beyond core SVDRP
capabilities a different approach is being used by the each extensions.
Prominent examples are:
- vdradmin (using native SVDRP and suffering from its performance,
optional use of direct file access to epg data)
- live-plugin (in
