Hi Odi, > It's very good! But I find it a bit focussed on a "bad practice" > solution often endorsed by hobbyists. Programmatic processing of HTML > pages is really not something you should do. HTML interfaces are for > humans not for computers. This should be pointed out.
You are absolutely right. I will add a disclaimer to the "Scenario" section. The document is not a recommendation on application design, it is meant as a collection of answers to questions I don't want to have to answer anymore :-) > I would like to see a more professional use case that uses an XML > interface for instance. Or one that downloads a document from a document > management system. I haven't seen too many questions on this kind of usage on the mailing list. I assume that people working on such scenarios are skilled enough to make effective use of the documentation we already have. Or they are asking specific questions, for example about how to do authentication. Still, documentations about recommended uses are a good idea. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
