Hi Patrik, On 17.11.2011 14:12, [email protected] wrote: > From: Patrik Flykt <[email protected]> > > Hi, > > Here's an attempt of requesting OpenConnect cookies through the Agent API. > > Two new fields are introduced to be used by the 'RequestInput' Agent API > D-Bus method call, 'OpenConnect.Cookie' and 'Hostname', as well as a 'Value' > argument (patch 01). The 'Hostname' field will contain the name of the > openconnect host in its 'Value' argument. The 'Hostname' field does not set > a 'Requirement' attribute, thus making the 'Hostname' field informative only > for the Agent. > > Agent API support is added in a straightforward fashion with the above fields > added to the 'RequestInput' method call (patch 02). As the function is to > be used from the openconnect vpn plugin, a new 'agent.h' header file with the > function prototype has been created.
I might miss something important here, but if I understand your approach correctly, you will tie the OpenConnect plugin into the core. Is this right? I mean we have this nice abstraction with provider where we try hard to separate the plugins from the core. Maybe it would be possible to do this in a more generic form. Or is this not possible? cheers, daniel _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
