From: "deckerben" <deckerben AT freenet DOT de>
Newsgroups: comp.os.msdos.djgpp
References: <3ce7fc1f$0$26970$9b622d9e AT news DOT freenet DOT de> <3CE810BA DOT FCA8CEDF AT phekda DOT freeserve DOT co DOT uk> <3ce8232a$0$26959$9b622d9e AT news DOT freenet DOT de> <3CE93EB2 DOT 2DD59789 AT phekda DOT freeserve DOT co DOT uk> <3ce97174$0$23709$9b622d9e AT news DOT freenet DOT de> <3CEAC1D9 DOT BAEA250F AT phekda DOT freeserve DOT co DOT uk>
Subject: Re: ANNOUNCEMENT: Python 2.2.1 for DOS test release
Date: Mon, 27 May 2002 19:04:54 +0200
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Lines: 14
Message-ID: <3cf27e46$0$8375$9b622d9e@news.freenet.de>
NNTP-Posting-Host: 213.6.65.112
X-Trace: 1022524999 news.freenet.de 8375 213.6.65.112
X-Complaints-To: abuse AT freenet DOT de
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> When you say "tries its own connection via comm port", do you mean that
the
> program should make a connection via modem and run all the networking
> protocols itself? That's quite a task. Also it would not work very well on
a
> LAN.

True, but wouldn't it be even more challenging to build a module that
supports a large array of external DOS networking drivers? I don't think
that "one-size-fits-all" there, or am I mistaken?

Ben