powercisco
Super VIP
- Messages
- 9,100
OScam svn7314
- Changeset [7314] by gf
dvbapi: Sent data as one packet. Some time ago I've sent a patch for generic dvbapi under linux (boxtype=pc).
It is working fine but I think there is need for one important enhancement.
Currently it is sending each CA_SET_PID and CA_SET_DESCR as two separate
packets which are: the request integer and the data. I think it will be
much better to sent it in one packet.
At first it is not elegant to sent it this way, besides the UDP packet
order is not the think that we should rely on.
About client implementation: as far as I know there is currently two
clients using the api: vdr-plugin-dvbapi and ostryck MuMuDVB fork
(maybe tvheadend will also use it). I contacted ostryck and he said
there will be no problem with this small api change. Obviously also
no problem on vdr-plugin-dvbapi side.
Patch by manio posted in ticket #2719.
thanks LePouSAT
- Changeset [7314] by gf
dvbapi: Sent data as one packet. Some time ago I've sent a patch for generic dvbapi under linux (boxtype=pc).
It is working fine but I think there is need for one important enhancement.
Currently it is sending each CA_SET_PID and CA_SET_DESCR as two separate
packets which are: the request integer and the data. I think it will be
much better to sent it in one packet.
At first it is not elegant to sent it this way, besides the UDP packet
order is not the think that we should rely on.
About client implementation: as far as I know there is currently two
clients using the api: vdr-plugin-dvbapi and ostryck MuMuDVB fork
(maybe tvheadend will also use it). I contacted ostryck and he said
there will be no problem with this small api change. Obviously also
no problem on vdr-plugin-dvbapi side.
Patch by manio posted in ticket #2719.
thanks LePouSAT