• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: localhost comm btwn X and Classic w/o LAN??
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: localhost comm btwn X and Classic w/o LAN??


  • Subject: Re: localhost comm btwn X and Classic w/o LAN??
  • From: Justin Walker <email@hidden>
  • Date: Wed, 10 Mar 2004 17:32:31 -0800

On Wednesday, March 10, 2004, at 05:12 PM, Mark Coniglio wrote:

I have an OS X mach-o application and a Classic code resource that need low latency communications. I have accomplished this by sending UDP messages between the two. The problem is that my application doesn't seem to work when there isn't an Ethernet cable plugged in.

For better or worse, that's the way it's designed. The aim was to minimize the changes to the code running in Classic, so we hooked Classic and Mac OS X up with a common IP address by having Classic use a faux driver that is an ethernet. This needs an ethernet driver in Mac OS X to communicate with. Without a valid ethernet device configured in Mac OS X, Classic thinks there is no networking device available, and refuses to play.

You could try this, but it's not guaranteed to work in all, or any, cases:
- pick an interface (e.g., en0)
- configure it using 'ifconfig':
ifconfig en0 inet 192.168.10.2 netmask 255.255.255.0 up
and see if that takes ("ifconfig en0").
- if it does, it's possible that Classic<->Mac OS X will work. I can't guarantee that the rest of Mac OS X will be happy with this, but it's worth a shot.

Regards,

Justin

Regards,

Justin


Is there a way to use networking to pass messages between a X and Classic, even if there is no Ethernet port (or AirPort) active?

Now, on OS X, if I ping 127.0.0.1 it always works, even without an active TCP/IP port (i.e., no Ethernet cable plugged in). So I suspect that Classic is the culprit here. Of course, that means that I'm using Open Transport...

What about multicasting? Would that help?

I may have to resort to Apple Events, but the latency was, realtively speaking, high.

Best Wishes,
Mark
--
Read about Troika Ranch in the March Apple Hot News:
http://www.apple.com/hotnews/articles/2003/03/troikaranch/

=====================================================================
Mark Coniglio, Artistic Co-Director | email@hidden
Troika Ranch Dance Theater | http://www.troikaranch.org
=====================================================================
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.


--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics | Some people have a mental
| horizon of radius zero, and
| call it their point of view.
| -- David Hilbert
*--------------------------------------*-------------------------------*
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.


References: 
 >localhost comm btwn X and Classic w/o LAN?? (From: Mark Coniglio <email@hidden>)

  • Prev by Date: localhost comm btwn X and Classic w/o LAN??
  • Next by Date: Re: localhost comm btwn X and Classic w/o LAN??
  • Previous by thread: localhost comm btwn X and Classic w/o LAN??
  • Next by thread: Re: localhost comm btwn X and Classic w/o LAN??
  • Index(es):
    • Date
    • Thread