If you're going to even think of using callbacks like they do in
Javascript, strongly reconsider. Especially so since the Javascript
community are abandoning callbacks in favour of promises, especially
of the A+ sort.
(Squeak has such Promises in the base image, and if anyone's
interested I can
Am 29.10.2013 um 10:56 schrieb Frank Shearar frank.shea...@gmail.com:
If you're going to even think of using callbacks like they do in
Javascript, strongly reconsider. Especially so since the Javascript
community are abandoning callbacks in favour of promises, especially
of the A+ sort.
Am 29.10.2013 um 02:08 schrieb David T. Lewis le...@mail.msen.com:
I have some experience with this, not related to Smalltalk but maybe
still relevant. I have worked with systems that were designed around
networked message passing, implemented on platforms like MS-DOS with time
slicing
On 29 October 2013 02:08, David T. Lewis le...@mail.msen.com wrote:
I have some experience with this, not related to Smalltalk but maybe
still relevant. I have worked with systems that were designed around
networked message passing, implemented on platforms like MS-DOS with time
slicing
Am 29.10.2013 um 02:08 schrieb David T. Lewis le...@mail.msen.com:
I have some experience with this, not related to Smalltalk but maybe
still relevant. I have worked with systems that were designed around
networked message passing, implemented on platforms like MS-DOS with
time
slicing
On 29 October 2013 02:08, David T. Lewis le...@mail.msen.com wrote:
I have some experience with this, not related to Smalltalk but maybe
still relevant. I have worked with systems that were designed around
networked message passing, implemented on platforms like MS-DOS with
time
slicing
Testing with real sockets, across multiple images is the only way I
would trust my own networking programs. OSProcess makes that an easy,
one-click affair.
On Mon, Oct 28, 2013 at 5:50 PM, Norbert Hartl norb...@hartl.name wrote:
I’m working on project that deals with server to server
Chris,
Am 29.10.2013 um 22:35 schrieb Chris Muller asquea...@gmail.com:
Testing with real sockets, across multiple images is the only way I
would trust my own networking programs. OSProcess makes that an easy,
one-click affair.
Agreed. That is what we do in addition. I’m doing tests for
I’m working on project that deals with server to server communication. For the
test suite it is necessary to simulate the two ends of the communication within
one test. The problem is that in a single threaded environment you make a send
call SC from server A to B but the response of B will
Am 28.10.2013 um 23:50 schrieb Norbert Hartl norb...@hartl.name:
Are there any approaches to simulate coroutines in a single thread
environment or approaches to deal with multiple processes within one process?
That should have been
Are there any approaches to simulate coroutines in a
you can do stuff like that, just not sync (which when it's about networks is a
good idea)
sounds like you should design things javascript style.
I mean, like if everything is a callback reacting to something..
yourAPIClient sendCommand: aCommand do: aBlockHandlingResponse
my 2 cents
On
Maybe i'm off track, but here my thoughts:
- one big misconception (and most problems which arising from it), that
people tend to use a bidirectional communication models instead of
unidirectional.
In bidirectional you tend to think as if you using same channel for sending
and receiving data.
I have some experience with this, not related to Smalltalk but maybe
still relevant. I have worked with systems that were designed around
networked message passing, implemented on platforms like MS-DOS with time
slicing kernels, Series I, OS/2, etc. These systems were designed to operate
with
13 matches
Mail list logo
