🚀 go-pugleaf

In article <1989Sep15.233027.7278@NCoast.ORG> davewt@ncoast.ORG (David Wright) writes:
>	From what I saw in the XPRZ (XPR Z modems library), there is a
>seperate library for each protocol. That gets around the problem you talk
>about, as there is not one xpr library, but one for each protocol. According
>to his instructions, programs could look for libraries that start with
>"xpr", or could directly be configured for the xpr libraries that were
>available.
>	Didn't you get the XPRZ library .zoo?

Sorry, David, but you are the one that should read the XPR protocol spec :-)
Yes, there is a separate "external" XPR library for each protocol, but this
is fine ONLY when a program runs a SINGLE external protocol at a time.  When
writing a BBS program that allows MULTIPLE connections (with multi-serial cards
like ASDG's Dual Serial Boards, for example), the sources provided won't work
because there is ONLY ONE XPRProtocolBase pointer that hold the library base
address to access the 4 (now 6) XPR functions.  What we (myself and Willy) 
suggest for that problem is an "array" of XPRProtocolBase pointers, one for
each "port" that the BBS program supports.  These pointers could be either
statically or dynamically allocated (in the first case one has to limit the 
number of concurrent protocols).  If this is done, then one user could use 
XPRkermit on serial.device, XPRzmodem on siosbx, Unit 0, and so on.

-- Marco Papa 'Doc'
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
uucp:...!pollux!papa       BIX:papa       ARPAnet:pollux!papa@oberon.usc.edu
"There's Alpha, Beta, Gamma, Diga and Caligari!" -- Rick Unland
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=