Jump to:
[Indrek's Bugs]
[Rich's Bugs]
[Rich's To-dos]
If you find any bugs or problems with libsocket, please
mail me with the details (i.e.
the program code and a description).
There are some (there must be), but I don't have anything very
nasty in mind. Most bugs are misfeatures, which means some things don't
work as they're supposed to.
- ioctl() partly works
- fcntl() partly works
- Lack of Winsock 2 support
[Top]
gethostname() will return a space-free version of the host name,
which may not be the DNS name.
Connecting to non-existent IP addresses seems to hang the library and
not time-out - why? How long is the time-out?
Non-blocking sockets are blocking?
libsocket isn't aware of the connection being closed by the
other end?
The include files need tidying up badly.
[Top]
Here are some things I plan to add when I have time:
Better documentation (as always) - any comments on how I can improve it
would be appreciated.
Add a Windows set-up program. This should be able to detect settings
automatically, making the library easier to use, not just by programmers, but
by end-users too.
Check that libsocket works with the DJGPP version 2.02 (currently in
alpha).
Tidy up the code - more consistent comments, etc.
Write some documentation about the library's internal functions, for
those who want to know.
Packet driver support? (e.g. like WAT/TCP, maybe using
ndispkt3?)
Test with threading libraries such as lwp for multi-threaded network
applications.
Overhaul the resolver code - it uses 'goto's! Besides, the extra code is
bolted-on rather than integrated.
Resolver issues: Implement reorder_addrs() in the resolver, when I know
what it does! Add support for hosts.equiv.
Write some documentation about WSOCK.VXD.
[Top]
The layout of this page is by Indrek Mandre, and the content is by
Richard Dawe.
|