By "provider" here I understand you to mean [for example] Sky UK, or Sky NZ, or Canal Digitaal. Although I think there is absolutely a place for this, I'd also like our "ad-hoc" EPG support to be better.We then can create/update provider support without massive updates to the TSwriter.
Do you consider the code language or managed vs. unmanaged as important?This is the entire reason I wish to move it into C#...
For me, the answer would have to be one that allows clean and efficient handling for time sensitive operations like constant now/next grabbing. Ideally there should be some decoupling between the real-time packet handling that TsWriter has to do and the full EPG data parsing and handling to avoid the possibility of any plugin affecting recording and timeshifting when EPG is grabbed. Whether it is desirable to write the EPG packets into a file to get this separation is something that I'm not certain about. This is the sort of decision I would ask other people on the team about.The only issue is getting the data from the TSWriter --> TV Server
Do we Marshall the data from C++ to C# or as I have in the custom data thread, write a seperate TS file with the data packets in it and read it from the TV Server. Or just write all the data along with the Video and Audio.
I think MHEG applications should be considered separately as the data should go to the client (to allow per-client application interactions). If you are referring to plugins to strip the MHEG guide data out then that would be a different story. I note that currently teletext seems to be either handled by or parsed and cached on the server - I think that this handling should be moved to the client side as well.If there is an optional data file then other features such as MHEG5 could be added to the TV Plugins as the data is there to be used.