Oh, ok, thanks.
This should work. I'll give it a try this evening.
Thanks,
Joern.
On 03.03.2010, at 09:06, Ceki Gülcü wrote:
Hello Joern,
You check whether a file is new within the call to your encoders
init methsod. Here is an example:
class MyEncoder implements Encoder {
void init(Ou
Hello Joern,
You check whether a file is new within the call to your encoders init methsod.
Here is an example:
class MyEncoder implements Encoder {
void init(OutputStream os) throws IOException {
// this should be always true
if(os instanceof ResilientFileOutputStream) {
Res
Hm, Lilith couldn't handle this at the moment and it would be pretty
hard to implement it, too.
There would be a rather big magic value instead of the amount of bytes
the next event consists of.
That magic value is actually written by a FileHeaderStrategy
implementation, DefaultFileHeader
My initial reaction is to let the encoder/decoder deal with this issue. Since
the encoder can always write its header when its init() method is called, the
decoder should check for file headers when it is reading in the stream.
On 02/03/2010 2:26 PM, Joern Huxhorn wrote:
Hi Ceki,
did you ha
Hi Ceki,
did you have the chance to think about a solution concerning the
remaining issue of http://jira.qos.ch/browse/LBCORE-128 - namely the
missing info about whether the stream is a fresh one or one that is
appending to an already existing one?
Regards & Thanks,
Joern.
On 02.03.2010,
Hello,
This is to inform you that I have merge the encoder branch into the
master branch. I am still documenting the changes. In short,
WriterAppeder has been renamed as OutputStreamAppender, FileAppender
now sub-classing the latter. OutputStreamAppender and sub-classes now
take an Encoder inste
