W3C home > Mailing lists > Public > www-lib@w3.org > July to September 2003

RE: Http Content Expire and Content Length BUG in LIBWWW

From: Sinha, Raj (Raj) <rajsinha@avaya.com>
Date: Wed, 17 Sep 2003 16:03:39 -0400
Message-ID: <8CA1128D59AD27429985B397118CEDDF019E315B@nj7460avexu1.global.avaya.com>
To: "Richard Atterer" <richard@list03.atterer.net>
Cc: <www-lib@w3.org>

Thanks That worked...:-)
Further more does anyone have ideas to implement a push type of service> I am looking for some architectural advice. 

Would love to use the Libwww to do the above since I already have a fully working HTTP client running. 

I was thinking of implementing a server and accept "post" kind of messages. However I believe using Libwww as a client and a server may not work well.

Anyone have any experience with this. I truly appreciate any advice, help etc


Raj Sinha

-----Original Message-----
From: Richard Atterer [mailto:richard@list03.atterer.net] 
Sent: Tuesday, September 16, 2003 1:02 PM
To: Sinha, Raj (Raj)
Cc: www-lib@w3.org
Subject: Re: Http Content Expire and Content Length BUG in LIBWWW

On Tue, Sep 16, 2003 at 10:33:21AM -0400, Sinha, Raj (Raj) wrote:
> However having done that I see that the Libwww gives me a value of -1 
> for content length for the resource.
> 	HTParentAnchor * entity = HTRequest_entityAnchor(me->request);
> 	content_len = HTAnchor_length(entity);

Have you tried HTResponse_length(HTRequest_response(me->request)) ? (I see the same problem with HTAnchor_length().)



  __   _
  |_) /|  Richard Atterer     |  GnuPG key:
  | \/|  http://atterer.net  |  0x888354F7
Received on Wednesday, 17 September 2003 16:03:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:33:56 UTC