Re: FW: Your binaries are great, but...

> I am implementing a tiny one-post client DLL on NT, and libwww has
> proven to be
> difficult (I couldn't us Perl for an app-specific reason).
> 
> I found that HTML_dtd is not in a library, so I put it into my
> project.
> 
> I almost got everything to link, when I added
> HTProfile_newNoCacheClient() to my code.

The current profiles initialize a large set of features - this is
described in

	http://www.w3.org/Library/User/Start.html

linked from

	http://www.w3.org/Library/User/#Use

It may very well be that we need more simple profiles as well. If you
have a good combination that you like then send it to the list and we
can add it to the list of libwww profiles.

Because of the large set of hooks and features in libwww and the
diversity of the applications using it, it is impossible to provide a
complete set of profiles that fit everybody's need.

> It seems that the profiles are not in the DLLs, so I added HTProfil.c to
> my
> project.  Then many more references were needed, including many I won't
> use.

You can find an example of a small setup in 

	http://www.w3.org/Library/Examples/libapp_2.c

linked from

	http://www.w3.org/Library/Examples/
 
> I will use the HTML parser, so converters are needed.
> I do one GET for a remote html file (it is parsed and fed to
> HTBlackHole()),
> and one POST (so I need application/x-www-form-urlencoded).  Do I need
> the
> default encoders for doing the url-encoding?

No, the url-encoding is not done as a stream (although you're right that
it could have been). It's part of

	http://www.w3.org/Library/src/HTAccess.html

which is part of 

	http://www.w3.org/Library/src/WWWApp.html
 
> I'm pretty sure I don't need files (HTFileInit() is not in the DLLs),
> mime or many other things in the profile.

Look in the profiles and see the set of features that they set up - then
select the ones that you like and write your own profile.

Henrik

Received on Tuesday, 22 December 1998 10:25:06 UTC