Re: Top three problems with libwww

There should be more examples.
Simple caching proxy, gateway, server
(not only clients).
It would be good if some code fragments were included in HTML doc's. (examples of using functions).

Profiles: more non-client profiles.
Profiles that reduce LibWWW redundancy for
concrete apps.

It would be good to have something like a class
diagram in documentation.

> Now when several of you are getting into libwww it would be nice if we
> can capture the places that you find are the most difficult to
> understand/use. I have a hard time figuring this out myself - your help
> would be much better.
> 
> For example, are the profiles ok? Where and how can the documentation be
> improved - or is it better with more sample apps? The eventloop seems to
> cause problems - how can it be explained better?
> 
> Now, there are 798 people who have checked out the code - and if ust a
> few of you are willing to help improve the tough spots then we can quite
> realistically improve it in a fast an efficient manner.
> 
> Henrik
> 
> 
> 



-----
See the original message at http://www.egroups.com/list/www-lib/?start=750

Received on Tuesday, 22 December 1998 11:19:05 UTC