Re: CapTP bug: "search path must not be empty" when identified but not onTheAir

On Feb 23, 2008, at 16:14, Mark Miller wrote:
> On Sat, Feb 23, 2008 at 12:16 PM, Kevin Reid <[email protected]> wrote:
>>  Perhaps SturdyRefs should not ever have search-path data for the
>>  local vat? (<captp> would insert it into the generated URLs,  
>> though.)
>
> SturdyRefs are usable, and passable-by-construction, without being
> turned into URLs. Don't they need this search-path data for these
> other uses?

Since SturdyRefs are uncalled via the <captp> loader, the search-path  
could be inserted by <captp> on uncall, and discarded on call  
(construction).

Not storing local search-path info also seems to me to have the  
advantage that, if a vat is relocated (i.e. the best search-path to  
reach it changes),  any SturdyRefs it keeps (in order to pass out) do  
not have to be replaced.

Or should systems be built with the assumption that completely fresh  
SturdyRefs (new swiss number as well) are handed out regularly anyway?


If we don't do this, what alternative do you see for the  
implementation of makeKnown (or other export-a-reference operations)  
while not onTheAir? Should they just fail explicitly?


Of course, this is all irrelevant (if I understand correctly) when  
the introducer has been pre-configured (by props) with an address to  
bind to, since the search path information is then available before  
onTheAir.

-- 
Kevin Reid                            <http://homepage.mac.com/kpreid/>