Re: Porting MOO objects

• Date: Tue, 28 Nov 1995 18:11:16 PST
• From:
  Kipp the Kidd <mcmudge@mailbox.syr.edu>
• Cc: Madhu Rao <mrao@site.gmu.edu>, list moo-cow <moo-cows@parc.xerox.com>
• Content-Type: TEXT/PLAIN; charset=US-ASCII
• In-Reply-To: <Pine.SUN.3.91.951128152724.18388A-100000@lance>

On Tue, 28 Nov 1995 david@castle.net wrote:

> There is a verb that I have run across on alot of MOO's that does this 
> and I have a copy even on my MOO.  Its called @autoport(on most places).  

I have a similar but much smaller verb on MOO2000 simply called '@port'
You type '@port <address> at <port>' and answer all the questions it asks.
If you want the code... get the property '$wiz.drop' and the verb 
'$wiz:@port'  this code ports objects from any LambdaCore MOO to the 
local MOO as long as you're a wiz at the destination MOO...  here's a 
sample run:

@port lambda.xerox.com at 8888
Connection string?
connect Myname Mypassword
Object to port?
#123456
Parent object?
$room
Are theese correct?
yes
>> [welcome to lambda MOO etc]
>> *** Connected, you have mail, etc.
>> That object does not define that verb. (sometimes does that.  It is 
  not a bug.  I did this because the port program sends a porting verb to 
  the remove MOO and wants to make sure the previous one is not there)
>> Porting #123456 (Foo object that you'd wanna port)
>> Porting verbs (E_PERMs, if any)
>> Porting properties (or E_PERMs)
>> Porting values (E_PERMs, if any)
>> Done porting
>> *** Disconnected ***
Object:  #123 (Ported Foo object that you'd wanna port)


This code works great with lambda beacuse it uses all builtin functions 
and can (normally) port an object without doing a laggy suspend()

- Kipp

• Re: Porting MOO objects
• From: david@castle.net

• Prev: Re: Porting MOO objects
• Next: Re: Porting MOO objects
• Index: MOO-cows
• Thread: MOO-cows