Re: Fwd: Chat with [email protected]

On Sat, Sep 19, 2009 at 12:11 PM, Kevin Reid <[email protected]> wrote:
> On Sep 19, 2009, at 12:04, Mark Miller wrote:
>
>> There are four protocol transitions CapTP needs to make. Given the
>> current minuscule adoption, I'm inclined to make all four changes
>> simultaneously and not worry about compatibility.
>>
>> * Switching from our custom DataComm to a VatTP layered on top of TLS.
>> Tyler and Kevin have both made progress towards this goal.
>
> I have done nothing related to this, but I agree it is the goal.

I thought you had in E-on-CommonLisp. My mistake. Also, for Caja-CapTP
running as JavaScript in the browser, there's really no other choice
anyway.


>> * Change the exposed object APIs (esp the Miranda Methods) to
>> something more language neutral, as already adopted by Caja-CapTP, so
>> that Caja-CapTP and E-CapTP can interoperate better.
>
> I have done nothing related to this, and I do not know what could be
> 'more language neutral' and still accomplish the goals
> straightforwardly, besides placing them as out-of-band CapTP messages.
>
> The only thing Caja-CapTP does in particular is give the miranda
> messages[*] longer names (to reduce the chance of conflicts with
> existing JavaScript programs) and only incorporate the ones which are
> necessary to CapTP.
>
>
>
> [*] I distinguish between the miranda protocol, those significant
> messages, and the miranda *methods*, the default implementation thereof.

Yes, I had in mind your more explicit Miranda message names.


-- 
Text by me above is hereby placed in the public domain

    Cheers,
    --MarkM