:And you can include all of these things in a set of standard-routines
:that go with any JoyNet application, and might be updated any time.
:An application programmer could just take this standard set of
:routines, and build his/her application around it, not worrying about
:the internals of these standard routines. Like with drivers for
:equipment, you could have updates of these drivers later on, and
:application software would be easily modified (maybe not even) to
:include these newer versions, whenever these become available.
Hey, hey, I'm working on it... (not too hard, but whatever).
But I fully agree to this.
:And hey, you'll have to put together some of these standard-routines
:at some time, how are you gonna call this a standard otherwise?
The cable is the standard, not the software (although it has got some
restrictions). Any program (i.e. a game) can use its own protocol, for it
won't have to communicate with other programs than the same on another
computer. Which uses the same protocol. If you really want to make some
network-programs, which will all have to be able to 'understand' eachothers
transfers, then you might develop some standard PROTOCOL (which is not
specified in the JoyNet standard. It could be called i.e. JoyCom...).
But network-programs are not very useful for this. JoyNet is just a cheap,
simple-to-make cable which is meant to be used in games or maybe to transfer
some files from one computer to another. And a bonus is that it also
supports a network, for more than 2-player games.
But if one really wants to make a network, then you should just use SCSI or
so... it is developed for it, is much faster and a lot easier to use.
By the way, I think your (Alwin Henseler) mail is a pretty good 'article'...
Do you mind if I put it on my homepage, in some kind of 'tips' or
'ideas'-section???
Ah, my homepage... almost forgot.
The Official JoyNet homepage:
http://datax.cjb.net/
~Grauw
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
****