When compiling and --with-mysql is set, the software fails to build when MySQL v4 is being used. I'm trying to put together some patches now to fix it... -- -- Robin Hugh Johnson E-Mail : robbat2 <at> orbis-terrarum.net Home Page : http://www.orbis-terrarum.net/?l=people.robbat2 ICQ# : 30269588 or 41961639 GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
I have just committed the first piece of code for supporting IDNs (internationalized domain names). It is currently in a branch tagged 'IDN', but we are planning to merge back into mainstream as soon as possible. Regards, Martin.
On Wed, Feb 12, 2003 at 06:34:29PM +0100, Richard Atterer wrote:
> Pausing a download while leaving the connection open
> [...]
The code I posted was incorrect. It worked most of the time, but it failed
if you paused the download, then continued it, and then stopped it (by
deleting the request object), because the wrong HTEvent object was
re-registered when continuing.
The following code is hopefully correct - it Works For Me...
The part for finding the net object is the same:
/* The HTNet object whose socket we'll unregister from the event loop. This
will prevent more data from being delivered to it, effectively pausing
the request. */
HTNet* net = HTRequest_net(request);
unsigned protocol = HTProtocol_id(HTNet_protocol(net));
if (protocol == 21) {
/* Protocol is FTP, which uses a control connection (which corresponds to
the main HTNet object) and a data connection. We need the HTNet object
for the latter. */
ftp_ctrl* ctrl = static_cast<ftp_ctrl*>(HTNet_context(net));
net = ctrl->dnet;
}
But to pause the download, better use:
HTChannel* channel = HTHost_channel(HTNet_host(net));
HTEvent_unregister(HTChannel_socket(channel), HTEvent_READ);
(Continue reading)Hello, here is the patch of the day... I believe that HTHost_killPipe() does not behave correctly - it (or rather the private function killPipeline() called by it) should close the HTTP/1.1 pipelined connection. Most of the time, the fact that it doesn't close it is not a problem, because when the event object of the connection next receives some data, it notices that nobody is listening to it, and its correct reaction is to close the connection: Host Event.. host 0x82998b0 `localhost' closed connection. Host Event.. Host 0x82998b0 `localhost' had 255 extraneous bytes: `...' Host Event.. Host 0x82998b0 `localhost' had 255 extraneous bytes: `...' ... Host Event.. Host 0x82998b0 `localhost' had 255 extraneous bytes: `...' Host Event.. Host 0x82998b0 `localhost' had 255 extraneous bytes: `...' Host Event.. Host 0x82998b0 `localhost' had 202 extraneous bytes: `...' Channel..... Delete 0x8284290 with semaphore 0, status 0 Channel..... Delete input stream 0x82b7e40 from channel 0x8284290 Channel..... Delete input stream 0x82b7e40 from channel 0x8284290 Socket read. FREEING.... Socket write FREEING.... Net Manager. Decreasing active sockets to 0, 1 persistent sockets Channel..... Deleted 0x8284290, socket 9 Net Manager. 0 active sockets, decreasing persistent sockets to 0 Host info... removed host 0x82998b0 as persistent Timer....... Dispatch timer 0x81f8870 Timer....... Deleted expired timer 0x81f8870(Continue reading)
Greetings, I've spent some time digging through the mailing list archives trying to find out how to open more than one simultaneous HTTP request to a given host. I have found some older (> 2 years) posts that say "you can't". Can anyone tell me if this is still the case? Regards, Tim Serong -- -- tim.serong <at> conceiva.com http://www.conceiva.com
On Tue, Mar 04, 2003 at 06:14:09PM +1100, Tim Serong wrote: > I've spent some time digging through the mailing list archives trying to > find out how to open more than one simultaneous HTTP request to a given > host. I have found some older (> 2 years) posts that say "you can't". > Can anyone tell me if this is still the case? I think so, yes, at least for HTTP requests to the same port. However, IMHO this is a good decision, at least for pipelined HTTP hosts. (FTP/HTTP1.0 is a different matter.) As always with libwww, it's probably possible to play some dirty tricks to get around the limitation. For this, you somehow need to fool HTHost_new() into creating another host object. For example, it might be possible just to append "." to the hostname for a second connection. Cheers, Richard -- -- __ _ |_) /| Richard Atterer | CS student at the Technische | GnuPG key: | \/¯| http://atterer.net | Universität München, Germany | 0x888354F7 ¯ '` ¯
Richard Atterer wrote: > > As always with libwww, it's probably possible to play some > dirty tricks to > get around the limitation. For this, you somehow need to fool > HTHost_new() > into creating another host object. For example, it might be > possible just > to append "." to the hostname for a second connection. Thank you, but surely it can't be this easy? :) In HTHost_new, there's a 'while' loop labelled "Search the cache". Remove this loop, and the existing host is never found, so a new one is returned every time. Problem solved, assuming you never want to pipeline HTTP requests. The only other catch I can see so far is that HTHost_find will then be useless and/or unpredictable, but AFAICT this function is never actually called, at least not from within libwww. Dirty trick? Yes, I think so. I haven't tried FTP with it yet either... Regards, Tim Serong -- -- tim.serong <at> conceiva.com http://www.conceiva.com(Continue reading)
I am trying to get w3c to run and retrieve https pages. I have compiled and created shared libraries from openssl. After configuring libwww and building w3c and trying https I get the message Sorry, can't access resource http requests work fine though. has anyone got the ssl working with w3c? I am on uname -a = SunOS hwds3 5.8 Generic_108528-10 sun4u sparc SUNW,Sun-Blade-100
On Thu, 17 Oct 2002, Steven Gray wrote: > > Windows platform > libwww version 5.4.0 built as DLLs > NoCacheClient profile > Using HTLoadToFile with an "ftp://user:pwd <at> foo.bar/file" URL. > Note, an identically coded HTTP request "http://foo.bar/file" > does not cause this bug to occur. > > The above FTP URL causes a memory access violation to occur > within HTChannel_deleteAll() when I attempt cleanup via > HTProfile_delete().... I had the exact same problem, and after much digging found a patch from Peter Stamfest that solves it. The patch, along with an explanation, can be found at http://lists.w3.org/Archives/Public/www-lib/2000JulSep/0241.html > For me, the bandaid solution was to modify the implementation of > HTHost_getReadNet() with this ugly hack: > > PUBLIC HTNet * HTHost_getReadNet(HTHost * host) > { > #ifdef WIN32 /* !!!yikes!!! */ > if (IsBadReadPtr(host->pipeline, 1)) > return NULL; > #endif > return host ? (HTNet *) HTList_firstObject(host->pipeline) : NULL; > }(Continue reading)
Hi, I need to send a XML file to a servlet (http://localohost:8080/myservlet?<?xml ......) I've tried to solve this problem searching into the archive, but I don't found the solution. Please, help me! regards, Alessandro
RSS Feed1 | |
|---|---|
1 | |
1 | |
3 | |
2 | |
3 | |
1 | |
1 | |
2 | |
1 | |
3 | |
1 | |
2 | |
2 | |
3 | |
1 | |
1 | |
1 | |
5 | |
5 | |
1 | |
4 | |
4 | |
9 | |
9 | |
1 | |
6 | |
5 | |
2 | |
6 | |
2 | |
8 | |
3 | |
3 | |
9 | |
14 | |
18 | |
5 | |
10 | |
13 | |
5 | |
7 | |
9 | |
9 | |
8 | |
4 | |
12 | |
5 | |
9 | |
24 | |
6 | |
9 | |
8 | |
5 | |
17 | |
7 | |
10 | |
2 | |
6 | |
10 | |
47 | |
18 | |
12 | |
16 | |
53 | |
34 | |
33 | |
33 | |
25 | |
37 | |
8 | |
41 | |
13 | |
39 | |
18 | |
27 | |
35 | |
3 |
