From:	"Wojciech Galazka" <wojciech DOT galazka AT polkomtel DOT com DOT pl>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Ending development of libsocket
Date:	Tue, 6 Feb 2001 01:02:53 +0100
Organization:	NASK - www.nask.pl
Lines:	56
Message-ID:	<95ngpf$bk9$1@pippin.nask.waw.pl>
References:	<3A745502 DOT 497CA8DF AT phekda DOT freeserve DOT co DOT uk>
NNTP-Posting-Host:	wawhsa-233.dial.plusgsm.pl
X-Trace:	pippin.nask.waw.pl 981419633 11913 212.2.98.233 (6 Feb 2001 00:33:53 GMT)
X-Complaints-To:	usenet AT nask DOT pl
NNTP-Posting-Date:	Tue, 6 Feb 2001 00:33:53 +0000 (UTC)
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.2106.4
X-Newsreader:	Microsoft Outlook Express 4.72.2106.4
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Richard Dawe nwrote in a message
<3A745502 DOT 497CA8DF AT phekda DOT freeserve DOT co DOT uk>...
>Hello.
>
>As the title suggests, I am ending development of libsocket. I no longer
>have the time, energy or interest to keep on developing libsocket to a
>good standard. It's a bit sad, because I've learnt a lot since I took over
>maintainership from Indrek Mandre.
>
Hi,

I'd like to hear how libsocket users would like this library to be targeted
at? Which operating system
* Windows NT DOS-box - Cygwin is perhaps a better approach?
* Windows 9x/ME - ?
* plain DOS ?

Unless I'd grab more information
*where is one willing to use libsocket
* what are the 'must have'  features of this library and which ones are only
'nice to have'?
it's  very difficult to make this library 'well and alive'. This is because
one needs to develop a reasonable plan first.
For what seemed to me as a simple task - to provide long file name  API to
DJGPP under Windows NT - took me
almost a year. most of that time spent on testing and making the piece of
code 'compatible' with Microsoft's
So I assume it may take at least a year as well to come up with something
robust enough to make it useful
when it comes to libsocket

Since the mission is to develop a BSD compliant networking library then I'd
consider a entry level library that
supports:
* data link level
* ARP / RARP
* IP + fragmentation  (both IPv4 & INv6)
* ICMP
* UDP
* no TCP at the moment
* limited ioctls
* no selec()t, pool() (oh no , perhaps could anyone suggest select() under
DOS ?)
* no async i/o

Dave took the top-down approach, that is with wsock.vxd he got TCP and UDP
protocols and tried to go down to IP which is almost impossible under
Windows as most of the stack inrternals are undocumented
I'd opt for quite the opposite direction

PS
Could anyone, please, forward this to the dossock list, I can post at the
usenet only now

- Raw text -