On Thu, Jul 17, 2008 at 9:53 AM, Jens Alfke <[EMAIL PROTECTED]> wrote:
>
> On 17 Jul '08, at 6:13 AM, em wrote:
>
>> So, architecturally, for high speed transmission over a closed network
>> neighborhood of say 9 minis, isn't there something
>> like a "SuperSocket" that could co-ordinate these now
On 17 Jul '08, at 6:13 AM, em wrote:
So, architecturally, for high speed transmission over a closed
network neighborhood of say 9 minis, isn't there something
like a "SuperSocket" that could co-ordinate these now '3' streams of
info.
There's nothing "super" about it; just regular sockets.
time to check the specs,
but that was really an aside.
When speaking of 'concurrent network transmission' I didn't include WI-FI
(80211.n specifically), mistakenly thinking this was a bit
too slow. So, architecturally, for high speed transmission over a closed
network neighbo
Erm,
not sure if this is still cocoa. In terms of TCP/IP there is no device
to select,
its just the systems routing tables that decide which way to go ... so
no API needed.
Tom
Am 17.07.2008 um 14:04 schrieb Matt Gough:
On 17 Jul 2008, at 1:41pm, em wrote:
Every computer that Apple sel
On 17 Jul 2008, at 1:41pm, em wrote:
Every computer that Apple sells contains both fire-wire as well as
built-in Ethernet. Is there any generally re-useable technique
(API?) for utilizing
TCP/IP over both the built-in Ethernet connection as well as 'TCP-IP
over firewire' for high-speed ne
G'day all,
Every computer that Apple sells contains both fire-wire as well as built-in
Ethernet. Is there any generally re-useable technique (API?) for utilizing
TCP/IP over both the built-in Ethernet connection as well as 'TCP-IP over
firewire' for high-speed network transmission?
thanks,
em
_
