[Kdenlive-devel] command end
Rolf Dubitzky
dubitzky at pktw06.phy.tu-dresden.de
Mon Nov 25 14:00:25 UTC 2002
Hi,
I am not sure why you used non-blocking IO in the nullcutter, I think it makes
much more sense to use blocking IO (eventually in a seperate thread of
course), or am I missing something? Well, for now I just switched to blocking
IO, but we have to make sure that we know when a complete command sequence
has been send. One could think of parsing the XML but that will be very
complicated when the doc is incomplete. The easiest way (I can think of) is
to disallow empty lines (i.e. "\n\n") in commands and close every command
with an empty line. I think that's a very common technique for text based
protokolls.
If you agree, we should add that to the spec, or do you have a better idea?
Cheers,
Rolf
***************************************************************
Rolf Dubitzky
e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de
s-mail see http://hep.phy.tu-dresden.de/~dubitzky/
***************************************************************
More information about the Kdenlive
mailing list