Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!newsfeed.pitt.edu!gatech!usenet.eel.ufl.edu!spool.mu.edu!munnari.OZ.AU!metro!metro!news.cs.su.oz.au!tmx!news.tmx.com.au!news
From: Stephan Meyn <s.meyn@oose.com.au>
Subject: Re: Deriving from nil in VSW 3.0.1
Message-ID: <31200A80.72E0@oose.com.au>
Nntp-Posting-Host: 203.5.19.198
Sender: news@online.tmx.com.au (System Administrator)
Mime-Version: 1.0
X-Mailer: Mozilla 2.0b6a (WinNT; I)
Content-Type: text/plain; charset=us-ascii
Organization: Object Oriented Pty Ltd
Date: Tue, 13 Feb 1996 03:50:24 GMT
References: <4fcaj4$eq5@news.gem.co.za> <311ABF7E.660B@oose.com.au> <4fhjkr$3eq@news.gem.co.za>
Content-Transfer-Encoding: 7bit
Lines: 15

Peter Shrosbree wrote:
>  now.
> 
> >>    4. become: is rather slow.  Does anyone have any suggestions on
> >> improving its performance?
> >No, there is not much you can do. However, how often does it occur?
> 
> Well, I did find a way.  Instead of using become: to transform the
> object Proxy has an instance variable into which the object is
> deserialized.  All messages to the Proxy are then rerouted to the
> instance variable.  This is much faster.  It is also closer to the
> Proxy design pattern in Gamma, et al.How do you reroute the messages? If you use doesNotUnderstand: then 
you will find that your overall system takes a performance hit that is not
insignificant. What do you prefer, once slow when resolving the proxy or
slow for every message sent to the resolved object?
