| |
W0RLI > PSBBS 05.07.96 01:26l 51 Lines 2326 Bytes #-10321 (0) @ WW
BID : W0RLI30064
Read: GUEST
Subj: More ideas.
Path: DB0AAB<DB0KCP<DB0CZ<HB9EAS<F6KDL<DB0HOM<LX0PAC<ON7RC<ON1BWP<ON6AR<
F6CNB<PU3DTA<VE7ROB<VE7DIE<KB7WE<KB7CNN<WB7QEU<W0RLI
Sent: 960704/0956 30064@W0RLI.OR.USA.NOAM
Some random thoughts on shared code development.
Most of the existing bbs codes are written as monolithic single
applications. Another way to attack the problem is to use a
client/server model. In this model, each portion of the system
is created as a stand-alone module, and communicates with
other modules via well definied interefaces.
For example, some of the modules which a bbs system needs are a message
database; a user information database; a communications mechanism; etc.
Each of these could be created as stand-alone modules, communicating with
each other at run time via appropriate interfaces.
The advantage of doing the work in this manner is that each module can
be written and tested independently of the other modules, and modules
from various authors can be interchanged. Any sysop can choose which
modules they wish to use to create their "favorite" bbs system. Perhaps
the user database module from one author, the message database from another,
the CLOVER protocol connectivity from a third, and packet networking from
a fourth.
Another advantage is that the authors do not need to all use the same
language, compiler, or software development environment. As long as
they create modules that run in the same operating systems, all
modules can work together.
The disadvantage is that the interfaces need to be well defined
and public. It is hard work to create the interface specifications.
However, there is a start for one of the interfaces.
This specification describes the interface between a pair of
bbs systems communicating over a lossless channel to forward
messages. It leaves out the details of how the two bbs systems
establish and drop the connection. Those details depend on
the communication protocol used. No specification has been
created yet for any of the common protocols (packet, tor, etc.)
There are several other interface protocols in use. For example
the export/import protocol which descibes a standard mechanism
for bbs systems to exchange messages via the file system. The
problem with this protocol is that there are (at least) four
"standard" export/import protocols in use. It would be quite
valuable if there were a good definition for this protocol.
... Hank
---
Occam's 2nd rule: Eschew Obfuscation; Espouse Elucidation.
W0RLI@W0RLI.OR.USA.NOAM
Read previous mail | Read next mail
| |
