On 12/21/2015 05:05 AM, Ben Coman wrote:
On Mon, Dec 21, 2015 at 8:30 PM, Denis Kudriashov <[email protected]> wrote:
Hello
2015-12-20 19:54 GMT+01:00 Mariano Martinez Peck <[email protected]>:
That being said, I of course like the idea of distributing processing
across multiple images. No wonder, my PhD tool (Marea) and related
sub-projects (Fuel, Ghost proxies, etc) have something to do with the
mentioned topic. Dave already mentioned about RemoteTask, which was
something I was about to mention. There is also Seamless project (now used
by Remote Debugger stuff) and quite other tools. Finally, I think this
project may have a big percentage that could be considered as "research". So
having a PhD / master student working on this would also be nice. In fact,
maybe Denis Kudriashov might work on that topic??? (he is now in RMOD team).
Yes. This is what I'm doing now. At last weeks of this year I plan to finish
my improvements to Seamless. Then I will adapt system and tools for remote
usage. Main goal is allow work with remote images same way we work locally:
remote debugging, browsing, any kind of system navigation, editing code.
Cool. I'm looking forward to maybe one day working like that with a
minimal image on embedded hardware.
I look forward to it. There's some set of capabilities you can't get
with your daily java or any non-image based dev environment, which
leaves Pharo ruling the cloud. Give it a few years.
Have you thought about SecureSession as the session solution? It does
have advantages and disadvantages, if I may briefly proselytize,
advertise and pitch you on this good news of yours:
advantages:
a) no certificates used
b) no third parties involved
c) highly secure
d) performant with crypto plugins
e) code visibility: entirely in squeak, no platform code requirements
f) community support of native code
g) forward error correction and compression on the horizon, hopefully.
disadvantages:
a) not performant without plugins
b) in further development
c) protocol likely will change in a coordinated fashion
d) non-standard protocol
e) non-validated by appropriate federal validators, as good crypto
f) governments cannot crack it.
g) may be slower than existing solution.
there 7 for and 7 against for a neutral honest appraisal from the
author. Fair dinkum.
--
. .. ... ^,^ robert
Go Panthers!
