[jira] [Updated] (XERCESC-2207) Rationalise network accessors
[ https://issues.apache.org/jira/browse/XERCESC-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cantor updated XERCESC-2207: -- Issue Type: Improvement (was: Bug) > Rationalise network accessors > - > > Key: XERCESC-2207 > URL: https://issues.apache.org/jira/browse/XERCESC-2207 > Project: Xerces-C++ > Issue Type: Improvement > Components: Miscellaneous >Affects Versions: 3.3.0 >Reporter: Roger Leigh >Priority: Major > Fix For: 4.0.0 > > > We currently support four netaccessors: curl, winsock, socket and cfurl. And > also "none" if network support is disabled. > This makes the test matrix quite large. Additionally, with the recent push > to use HTTPS everywhere, I wonder about the dangers of Xerces using its own > plain HTTP implementation over sockets without any SSL support. > Would dropping socket and winsock, and requiring curl or cfurl make sense? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Updated] (XERCESC-2207) Rationalise network accessors
[ https://issues.apache.org/jira/browse/XERCESC-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Cantor updated XERCESC-2207: -- Affects Version/s: (was: 3.3.0) > Rationalise network accessors > - > > Key: XERCESC-2207 > URL: https://issues.apache.org/jira/browse/XERCESC-2207 > Project: Xerces-C++ > Issue Type: Improvement > Components: Miscellaneous >Reporter: Roger Leigh >Priority: Major > Fix For: 4.0.0 > > > We currently support four netaccessors: curl, winsock, socket and cfurl. And > also "none" if network support is disabled. > This makes the test matrix quite large. Additionally, with the recent push > to use HTTPS everywhere, I wonder about the dangers of Xerces using its own > plain HTTP implementation over sockets without any SSL support. > Would dropping socket and winsock, and requiring curl or cfurl make sense? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
[jira] [Updated] (XERCESC-2207) Rationalise network accessors
[ https://issues.apache.org/jira/browse/XERCESC-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Leigh updated XERCESC-2207: - Fix Version/s: (was: 3.3.0) 4.0.0 > Rationalise network accessors > - > > Key: XERCESC-2207 > URL: https://issues.apache.org/jira/browse/XERCESC-2207 > Project: Xerces-C++ > Issue Type: Bug > Components: Miscellaneous >Affects Versions: 3.3.0 >Reporter: Roger Leigh >Priority: Major > Fix For: 4.0.0 > > > We currently support four netaccessors: curl, winsock, socket and cfurl. And > also "none" if network support is disabled. > This makes the test matrix quite large. Additionally, with the recent push > to use HTTPS everywhere, I wonder about the dangers of Xerces using its own > plain HTTP implementation over sockets without any SSL support. > Would dropping socket and winsock, and requiring curl or cfurl make sense? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: c-dev-h...@xerces.apache.org
