Hi all, On 20/03/17 16:15, Tim Ruehsen wrote: > One goal would be to make up data structures and an API that can be extended > without breaking compatibility between wget2 and the plugin in the future. > E.g. a newer wget2 should still be able to work with an older plugin and vice > versa. >
I would add something to this. Maybe this is not 100% related to the plugin framework, but we need a consistent API to manipulate all stages of an HTTP request (connection establishment, SSL/TLS handshake, SSL/TLS cert verification, etc.) in a single place, as I once told Tim off-list. Have a look at #142 [0], for instance. Although it mentions HPKP, there are other parts that would benefit from this as well. I was thinking of an event-based framework (e.g. plugins subscribe to 'events' and get called when they happen). Tim, on the other hand, prefers a data structure where you could access all the details of a connection (e.g. something like 'wget_connection_t', with references to 'wget_tls_t', etc.), and this data structure gets passed to plugins and they decide what to do. [0] https://github.com/rockdaboot/wget2/issues/142 > Just make up a sketch of your ideas and we (you and one of our mentors) will > improve/discuss that. > > Regards, Tim >
signature.asc
Description: OpenPGP digital signature