mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu" <akaras...@apache.org>
Subject Re: [AsyncWeb] Client redesign
Date Mon, 11 Feb 2008 07:12:27 GMT
On Feb 11, 2008 1:28 AM, Mike Heath <mheath@apache.org> wrote:

> 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.

I like this layered approach.  I also like the list of features/usage
senarios especially AJAX/COMET centric features.  At some point I think we
need to have a similar discussion about this and the server.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message