Now I got your point. Well, it seems that you've sorted the problem out,
haven't you?

Cheers,

Jorge.

kan escreveu:
>
> On Jan 25, 6:51 pm, "Jorge Marques Pelizzoni" <[EMAIL PROTECTED]>
> wrote:
>
>> Ok. The problem is that it is a bit fuzzy where cryptopp is fitting in.
>> You mean skip x lines from (i) the raw input file or (ii) the
>> decrypted/decompressed/whatever file? If (ii) is the case, you should
> Sure, the (ii). To skip something in encrypted/compressed data is
> impossible ;)
>
>> create a special skipping filter, maybe even subclassing StringSink...
> Actually "skipping lines" was a simple example, in real situation in
> can be something complicated, e.g. if it will be SAX parser, it can
> skip tags. But to build own xml parser as Sink is not good idea. ;)
>
>> Then you might go pumping fixed-length blocks till your special sink
>> signals that what you've got what you want. ONLY THEN pass the data on
>> to
> I don't understand how to pass the data onto the xmlparser! I can pass
> data only onto memory (or file or other sink). In other words - sink
> should be stateless or state should be controlled by crypto. In my
> situation state is not under control, it's deeply inside libxml2
> library, it has own reading cycle.
>
>> the xmlparser. Your design that pumps from inside the callback function
>> will lead you nowhere, in my opinion ...
> But it works. ;)
> Just pump a little the source and try to catch something from end of
> filters chain.
>
>> It is perfectly possible to develop a sink that will enable you to keep
>> memory under control.
> Actually more correctly to say not "memory under control", but "flow
> control".
>
>
> >


Jorge M. Pelizzoni
ICMC - Universidade de São Paulo


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to [EMAIL PROTECTED]
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
-~----------~----~----~----~------~----~------~--~---

Reply via email to