[Pharo-project] mixing open and closed source within Pharo

Mariano Martinez Peck marianopeck at gmail.com
Sun Jun 3 09:52:07 EDT 2012


>
> (btw, I'm assuming CM bytecodes was a typo meant to be VM bytecodes? or
> otherwise what is CM?)
>
>
CompiledMethod ;)


>
>
>>
>>> 3. Running multiple images on a single VM such that the VM passing
>>> message
>>> calls efficiently between the two images like an "enterprise bus*" - one
>>> open source and one closed source.  Any common base objects between the
>>> images might be shared on a copy-on-write basis.
>>>
>>>
>>> What are your thoughts?
>>>
>>>
>>>
>>
>> I think option 3 is most vital:
>> you can communicate between two images like between two parties who
>> don't trust each other (so images should handshake, use encryption
>> key(s), and try to log-in one to other), then if succeed, one can be
>> able to see source code  use  remote debugger etc
>> Nothing new under the sun...
>>
>>
>>
>>> cheers -ben
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
>


-- 
Mariano
http://marianopeck.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20120603/7b21c2a1/attachment.html>


More information about the Pharo-dev mailing list