Re: CRC

• Date: Tue, 13 Feb 1996 10:39:52 PST
• From:
  mcmudge@mailbox.syr.edu (Kipp the Kidd)
• Content-Type: text/plain; charset="us-ascii"

At 03:35 AM 2/13/96 PST, Mark R. Bowyer wrote:
>Well, you *Could* use the standard CRC system for this, but why bother?
All you 
>want is a way of checking that the data you want has arrived in the form it 
>left?  Do you *really* want to try and repair this code if it arrives in a 
>damaged form, and more to the point, do you really want to do this in a
builtin, 
>with the whole MOO lagging while it does it?  I'd suggest using MPL to open a 
>clean connection between the MOOs (most of my @autoport errors have been
due to 
>other text getting in to the transfer, I think) and remembering that a certain 
>amount of packet checking gets done before you get to see it anyway.

I wasn't planning on using this to make sure the text got to the other MOO
correctly, I know it will since the network already uses some sort of CRC
checking.  What I wanted was for BOTH MOOs to generate a CRC of the object's
code.  If the CRCs match, the MOO will not update anything.  If it doesn't,
then the host MOO will update the client MOO's code... That way, this group
of objects will remain exactly the same on both MOOs, incase I decide to
alter one, I only have to do it once.

- Kipp
-----BEGIN GEEK CODE BLOCK-----
GCS/CC d- s+:- a16 C++ UL++++ P+ L++ E-? W+ !N--@ !o-- K->K++++++
w++(--) O- M-- V--? PS++(+) PE(--) Y+ PGP-? t+ 5(+) X++ R+++(*)
!tv b+ DI++++ D++++ G e* h!()(*) r+ !y+
------END GEEK CODE BLOCK------
-----BEGIN NOT SO GEEKY BLOCK-----
MOO projects:
  RPG Minimal.db:  paradigm.microwave.com 5000
  MOO2000:         moo.microwave.com 2000
  MundoHispano:    europa.syr.edu 8888
------END NOT SO GEEKY BLOCK------

• Prev: Re: CRC
• Next: Re: CRC
• Index: MOO-cows
• Thread: MOO-cows