I still dont know what opening has to do with transmitting, even when you do it remotely , a socket / websocket connection should be all you need. For me transmitting the entire image would be necessary only in the case you want to install it remotely and that remote location has no immediate access to the installation.��

On Fri, Aug 25, 2017 at 7:14 AM Ben Coman <btc@openinworld.com> wrote:
I understand that to mean effectively that you are "opening" the image across the net - so eventually you need to whole image transmitted, but you don't have to wait for the whole thing before you start running it.
cheers -ben


On Fri, Aug 25, 2017 at 2:00 AM, Dimitris Chloupis <kilon.alios@gmail.com> wrote:
Indeed that can be a barrier ��but why you would want to transmit an entire image instead of portion of it using something like fuel files or other binary formats ? It would dramatically reduce the size of data you transmit.��

On Thu, Aug 24, 2017 at 8:10 PM Craig Latta <craig@blackpagedigital.com> wrote:

> ...10mbs which is the size pharo image can be reduced to is nothing
> for todays TBs hard drives and GBs flash drives and online storage.
> Unless you do an embedded app and 10 mbs are huge for your limited
> storage.

�� �� ��Or you want to minimize initial startup time, including the time it
takes to transmit the entire system over the net.


-C

--
Craig Latta
Black Page Digital
Amsterdam :: San Francisco
craig@blackpagedigital.com
voice through 2017-09-12:
+ 1 510 833 5799 (SMS ok)
+31�� 20 893 2796 (no SMS)