Hi,
I have been discussing about that issue with Patrick Flykt and
since Jukka Rissanen's patch* has not been accepted I guess there
are still rooms for ideas/patch around.
What about then expanding the current struct connman_ipdevice in
ipdevice.c so that:
struct connman_ipdevice {
...
char *proxy;
struct proxy_config *proxy_configuration;
...
};
where:
struct proxy_config {
union {
char *pac;
struct proxy_manual_config *manual;
} config;
};
where:
struct proxy_manual_config {
char *http;
uint16_t http_port;
char https;
uint16_t https_port;
... as Jukka proposed* in struct connman_manual_proxy ...
};
From DBus api point of view, it keeps the same as it is now + the manual
config fields as Jukka proposed or would you prefer to get the manual
config fields in there own dict inside Proxy dict.
(a sub dict in a dict, is it really handy?)
In ipconfig.c this would just need to add support inside existing
getters/setters. No big changes in the api at least.
Anyway, what's the plan about pacrunner? As its name contains, I guess
it targets only PAC files. So I guess, we do not have to care about it
in case of manual config.
What about libproxy, is there any plan yet on creating a module for
connman in it?
What do you think? Any inputs?
Best regards,
Tomasz
*: see http://lists.connman.net/pipermail/connman/2010-August/001890.html
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
