Hi Jason,
We actually changed our network implementation long ago. The one
that is in sync with the tree is part of the private support library
and we won't be releasing source for it at this time. The one that
is in the repository and not in sync is in fact not used, but at one
time
On 17-Feb-08, at 2:27 PM, Alp Toker wrote:
Daniel Zucker wrote:
Hi Alp and Brent,
My vote is to use Wininet.
Hi Daniel,
You can register your vote by writing and offering to maintain a
WinINet
http backend.
We have already done one. You can find the source for it in our
Hi George,
Where can I find the source drop? Did you file a bug on http://bugs.webkit.org
or someplace? I don't see an obvious place on your torchmobile.com
site to grab it.
Thanks,
-Brent
On Feb 23, 2008, at 9:37 AM, George Staikos wrote:
On 17-Feb-08, at 2:27 PM, Alp Toker wrote:
On 23-Feb-08, at 9:08 PM, Brent Fulgham wrote:
I assume the click-through license is for the binary, not the
WebKit sources? I.e., the license seems to indicate that I may only
make one personal copy of the software, which is not in agreement
with the BSD/LGPL license of the WebKit
I assume the click-through license is for the binary, not the WebKit
sources? I.e., the license seems to indicate that I may only make one
personal copy of the software, which is not in agreement with the BSD/
LGPL license of the WebKit sources, correct?
On Feb 23, 2008, at 5:04 PM,
Hi Alp,
I am happy to contribute to this ongoing effort to make a Windows version of
WebKit free from Apple libraries.
I would prefer to wait until there is consensus from the community on the
best way to move forward, so that my coding effort is not wasted.
Cheers,
Dan
On Feb 17, 2008 11:27
Hi Alp and Brent,
My vote is to use Wininet.
This is because my objective is to eventually support a WinCE version.
Wininet is used in both Win32 and WinCE, so it is a convenient choice from
this point of view.
CURL would be OK if it could be easily ported to WinCE. I haven't looked
into that,
I'd like to see a pretty much pure open source solution available for
all platforms.
By pure I mean down to the core windowing and libc level.
As far as porting curl to WinCE.
Found this.
http://curl.haxx.se/mail/lib-2002-07/0085.html
A obvious reason to have this available is it makes it easier
Daniel Zucker wrote:
Hi Alp and Brent,
My vote is to use Wininet.
Hi Daniel,
You can register your vote by writing and offering to maintain a WinINet
http backend.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
Hi there,
Another option/alternative to Curl would be POCO - http://pocoproject.org
. It has the advantage of being nice C++ cross-platform code,
available for all major platforms. Already has nice HTTP(S) and FTP
client support.
Günter
On Feb 17, 2008, at 18:15 , Daniel Zucker wrote:
Hi Alp,
On Feb 14, 2008, at 2:05 AM, Alp Toker wrote:
Brent Fulgham wrote:
In the medium term, I will probably end up ripping out the
CFNetwork code to replace with native windows calls, though it
would be nice to avoid this needless work.
The CURL http backend used by the GTK+ and Wx
Hi Chris,
According to Apple's website (http://www.opensource.apple.com/darwinsource/10.5.2/
), Core Foundation Lite and CFNetwork are open source under the
APSL. However, current versions of these libraries do not seem to
actually be accessible (see
12 matches
Mail list logo
