So I dig this attachment concept, using sourced, transforms(filters),
sinks. However I don't dig the syntax and memory management aspects. I
understand there is Ref(), but I'd prefer a syntax like:
StringSource src(...);
Base64Decoder b64d(...);
NullFilter null(...);
StreamTransformationFilter stf(...);
StringSync sink(...);
AttachmentChain c; // theoretical class
c.link(src);
if (srcEncoding == "base64")
c.link(src);
c.link(stf);
c.link(sink);
c..execute();
or
AttachmentChain chain(src).link(b64d).link(stf).link(sink).execute();
So that these pipelines can be created in code. There seems to be a bias
towards a static pipeline configuration. ( ex:
https://www.cryptopp.com/wiki/Advanced_Encryption_Standard#Encrypting_a_string_using_AES
)
Aside from that the docs don't really cover in a simple way what the
sources are, the intermediate transforms and the outputs. It's be cool to
have some kind of reference (or interactive guide, where you could select
from dropdowns the source, add steps to the pipeline, and select the
destination). I did eventually figure this out, but it took some reading an
consulting the examples.
There may be a way to programmatically set up the pipeline dynamically, but
I haven't seen it yet. Is there a way to more dynamically structure the
pipeline?
--
--
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.
---
You received this message because you are subscribed to the Google Groups
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
