On Thu, 13 Jul 2000, Warren Young wrote:
> As maintainer of the Winsock Programmer's FAQ, I have a few interests in
> WINE's implementation of Winsock:
>
> 1. You state that your Winsock 1.1 implementation is at 90% completion.
> What has to be done before you call it 100%?
Well, to implement any routines that remain, and fix remaining bugs... for
example, I have strong doubts that OOB data is handled in all cases. Also
the blocking behaviour could be improved a bit, I'm not sure that it does
it correctly in every case either (especially not if OOB data is
involved).
> 2. The Wine status page says that the documentation for Winsock in WINE
> is somewhere between outdated and nonexistent. What do you need?
That docs don't exist doesn't mean that we need it, since there isn't much
the user really needs to know about Winsock. But since you ask, to
document how the winsock is implemented in Wine (the interaction between
the wineserver and the client, what is done where, how it keeps track of
socket state, and things like that) could be useful, to unconfuse
potential new developers and bughunters in the area.
> 3. What does your Winsock 2 provider support today, and what does it
> need in the near future? I.e., Is there any lack in the Winsock 2
> provider stopping you from getting to WINE 1.0?
Right now Wine's Winsock2 does exactly the same as Winsock1 (except that
WSAEventSelect is also implemented and available, that is). And other
Winsock 2 functionality would definitely not be a release-critical
component.
> 4. What about Winsock 2 support beyond 1.0? I imagine that this
> includes things like overlapped I/O, I/O completion ports, and the
> Service Provider Interface. Am I close?
There are no specific plans. People just implement what they want to have.
And there are no current efforts on Winsock functionality, unless
Macadamian is planning on something (though I doubt that they need
anything more than what already exists).
