Re: Concurrent network transmission
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 network transmission? thanks, Note - The MacBook Air does NOT have firewire. For those with Firewire you can set up a network interface to use it. In the Network System Preferences you can add/Enable Firewire as a connection. As for APIs, sorry don't know myself. Matt ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Concurrent network transmission
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 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, Note - The MacBook Air does NOT have firewire. For those with Firewire you can set up a network interface to use it. In the Network System Preferences you can add/Enable Firewire as a connection. As for APIs, sorry don't know myself. Matt ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/publictom%40mac.com This email sent to [EMAIL PROTECTED] ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Concurrent network transmission
Matt, much thanks for the correction to my inaccurate statement. If I'm not mistaken my 2.0Ghz G5 iMac has FW400--not FW800. Also the current minis have FW400 only. This is surprising since older models, i believe, had FW800--years ago. I could be wrong and I apaologize for not taking the 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 neighborhood of say 9 minis, isn't there something like a SuperSocket that could co-ordinate these now '3' streams of info. Forgive me for drawing an analogy, but the third computer I ever worked on was designed by Seymour Cray and the engineers at the time commented 'we just keep on throwing PPU's at it and it doesn't even blink. All the current chips/busses are quite a bit more poweful than this cdc6600 that was sitting at Purdue in the late 60's and certainly should be capable of supporting this technique. So, again, thanks for the correction--which might be the 'death knell' of firewire? -em On Thursday, July 17, 2008, at 07:04AM, Matt Gough [EMAIL PROTECTED] wrote: 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 network transmission? thanks, Note - The MacBook Air does NOT have firewire. For those with Firewire you can set up a network interface to use it. In the Network System Preferences you can add/Enable Firewire as a connection. As for APIs, sorry don't know myself. Matt ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Concurrent network transmission
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. OS X supports multihoming, so a single computer can have multiple network interfaces, each with its own IP address. If your program just opens a connection the usual way, just specifying the destination address and port, the kernel will decide which interface to route the packets through. (For example, if Ethernet only connects to the corporate intranet, but WiFi reaches a public base station, then connections to intranet IP addresses will be sent over Ethernet while those to public sites will go over WiFi.) In ambiguous cases, where a host is reachable via multiple interfaces, the BSD socket APIs allows you to bind a socket to one of your interfaces to force it to use that one. In your case, the minis can probably reach another one by WiFi as well as FireWire, so you could force them to use FireWire by binding a socket to that interface. (Globally, you can control this by adjusting the priority of the interfaces in the Network pref pane. If FireWire has a higher priority than Airport, which I think it does by default, then the kernel will choose it preferentially.) [This thread is more relevant to the macnetworkprog mailing list. You're more likely to reach networking gurus if you post over there.] —Jens smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
Re: Concurrent network transmission
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 '3' streams of info. There's nothing super about it; just regular sockets. OS X supports multihoming, so a single computer can have multiple network interfaces, each with its own IP address. I think he is talking about link fusing or link aggregation... (don't think you can aggregate ethernet and firewire given difference between the two). http://en.wikipedia.org/wiki/Link_Aggregation_Control_Protocol Combining Ethernet ports If you have a computer with more than one Ethernet port, you can combine them into one virtual Ethernet port. This is known as link aggregation. The combined Ethernet ports appear as a single IP address to your computer and applications. Combining ports provides increased bandwidth by merging the bandwidth of the individual ports. The network traffic is also balanced across the ports. In addition to balancing network traffic, combining ports provides automatic backup if one port or cable fails. All traffic that was routed over the failed port is rerouted to one of the remaining ports. This backup is automatic, and applications using the port continue without interruption. If the Ethernet ports you want to combine are on a PCI card installed in your computer, make sure the card is installed properly before combining the ports. See the documentation that came with the PCI card for instructions about installing it. To combine Ethernet ports: Choose Apple System Preferences, and then click Network. Choose Manage Virtual Interfaces from the Actions pop-up menu (looks like a gear) at the bottom of the network connection services list. Click Add (+) and choose New Link Aggregate. Select the Ethernet ports you want to combine, give the aggregate service a name, and then click Create. Click Apply Now to activate the new virtual Ethernet service. After the Ethernet ports have been linked, you can check the status of the link by looking at the icon in the network connection service list. For more detailed information about the aggregated link status, click one of the ports in the list. Mac OS X uses the Link Aggregation Control Protocol (LACP) to negotiate the link aggregation. LACP must be supported on all link aggregation devices involved. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
