[Date Prev][Date Next] [Chronological] [Thread] [Top]


On Tue, Aug 01, 2000 at 04:14:04PM +0200, Stephan Krings wrote:
> Hello,
> > I suggest that in your initial design/implement an ASYNC (in
> > the protocol sense, not system I/O sense) C++ API which
> > leverages the C API's ASYNC routines.  Once this is implemented,
> > then you can design a C++ SYNC API layered upon your C++ ASYNC
> > API.
> I also think, that this is a useful decision. The asynchronous
> approach is more general and can be used in a wider variety of
> applications. Once you have that (and mastered all the difficulties
> associated with it) it should be quite easy to get the synchronous API
> on top.
Yes, sounds quite reasonable to me, too. I think I will go this way. AFAIK
its kind of similar to the way the Java-API is implemented. They just didn't 
define extra classes for the async API. It's just an interface that 
implemented by the sync. Classes.