Jeff Genender wrote: > > David M. Lloyd wrote: >>> Yes, this is my thinking as well - the casual user wants a simplified API, >> while the advanced user wants a more detailed interface. >> > > Certainly no reason not to offer both capabilities ;-)
I totally agree. I think we should offer a very simple straight forward API for the simple cases where the developer only wants asynchronism and doesn't want to worry about the details. At the same time, there are some very complex use cases that we have to account for that would require a more complex API. I keep imaging providing a very flexible API that can accommodate large uploads/downloads, deal with chunked encoding and COMET technique, handle pipelining, etc. We could then wrap this flexible API with a simpler API for dealing with simple requests. For example, if all I want to do is a couple of simple GET requests, I should haven't to build an HttpRequest object. I should be able to provide a URL and do a simple GET. -Mike
