[Development] Notes from QtNetwork sessions

2012-06-25 Thread shane.kearns
Thanks due to Rich Moore for taking notes in the session, which I've edited my own into. * Built-in support for redirects (suggested by Yuval T.) * Flag on QNAM * Override on a per-request basis? * Set max count? (for avoiding redirect loops) * What about redirect from secure to non-secu

Re: [Development] Notes from QtNetwork sessions

2012-06-25 Thread Xizhi Zhu
Hi, Do we have the mutex / blocking issues for the bearer tracked on Jira? I guess it needs some design, including the blocking constructor, before we really start to fix it. > * The API currently lists the available wireless lans, thiago thinks that it > should not do this and should say that

Re: [Development] Notes from QtNetwork sessions

2012-06-25 Thread shane.kearns
From: Xizhi Zhu [mailto:xizhi@gmail.com] > Do we have the mutex / blocking issues for the bearer tracked on Jira? I > guess it needs some design, > including the blocking constructor, before we really start to fix it. There have been a number of issues in JIRA, most have been P1 emergencies f

Re: [Development] Notes from QtNetwork sessions

2012-06-25 Thread Thiago Macieira
On segunda-feira, 25 de junho de 2012 12.35.32, shane.kea...@accenture.com wrote: > My design thought is that the bearer backends (plugins) should only be > called from the bearer thread. That would mean having a proxy QObject in > the bearer thread that communicates via signals with the public API

Re: [Development] Notes from QtNetwork sessions

2012-06-25 Thread shane.kearns
> > Multihoming is actually quite common if you consider VPNs. > > (e.g. intranet traffic goes to the VPN, and everything else goes to > > the real network adaptor by default) > > When I think "multihoming", I think different routes to reach the same > server. > Usually, that means two default rout

Re: [Development] Notes from QtNetwork sessions

2012-06-25 Thread Rohan McGovern
shane.kea...@accenture.com said: > > * Autotests > * Non-significant > * Not compiled What is meant by "not compiled"? > * Dependency on the test server > * eg. QNetworkReply has too many tests they should be broken up > * Some tests should be recognised as possible to fail, unit tests

Re: [Development] Notes from QtNetwork sessions

2012-06-26 Thread shane.kearns
> > * Autotests > > * Non-significant > > * Not compiled > > What is meant by "not compiled"? Tests excluded from the parent .pro file (qnetworkproxyfactory used to be commented out, this has been fixed in 5.0 but not 4.8) Also use of contains(QT_CONFIG, private_tests) to exclude test cases