[NUT-devel] Info packets in NUT stream (spec bugs?)
michaelni at gmx.at
Sat Nov 4 22:23:58 CET 2006
On Sat, Nov 04, 2006 at 03:53:13PM +0200, Oded Shimon wrote:
> And I have an API question for libnut demuxer:
> for the case of info headers after main headers, I plan on looking for
> them only once and give them to the caller together with the main header
> information, but what should I do for the case of info packets found in
> the wild? optional callback function?
do you also have a callback for normal frames? if yes then it seems the
right spot for info packets too, if you have no callbacks then one for
info packets looks odd too IMHO
you could also simply set a flag if info packets changed, and the user
could check that after each packet if needed, or ...
really i dont know what is best ...
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
In the past you could go to a library and read, borrow or copy any book
Today you'd get arrested for mere telling someone where the library is
More information about the NUT-devel