Re: sockets in Powerplant?
Re: sockets in Powerplant?
- Subject: Re: sockets in Powerplant?
- From: Lyndsey Ferguson <email@hidden>
- Date: Fri, 17 Oct 2003 17:37:56 -0400
I worked with OpenTransport to create a class that matched our Windows
version of the Socket wrapper. I'm not a super experienced network
programmer, but I broadcast to the computer's LAN and am able to receive it
on other computers. I forget what you wrote, but does using tcpdump in the
terminal show no data being transmitted? Are you checking for errors in the
debugger after the broadcast call is made? I simply created a UDP
OpenTransport Endpoint and sent a message to 0x7F000001 for the node and my
port number in the port portion.
What errors appear when you try to send the message?
On 10/17/03 5:22 PM, "Marc Stibane" <email@hidden> wrote:
>
Since nobody answered my question yet, I describe what I've tried already:
>
I ran into a heap of (compiler and linker) probs when I tried to
>
eliminate the glue code which bridges the "socket" application routines
>
to OpenTransport and use native sockets instead.
>
>
I made a new Mach-O target, and a new "glue" file to native sockets,
>
which would include <sys/socket.h>. Turned out, I needed to include
>
<netdb.h>, which then gave duplicate definitions errors with MSL. OK,
>
tried to get rid of MSL - bummer.
>
PowerPlant needs the MSL <exceptions>.
>
Does anyone have a (patched) PowerPlant which doesn't need MSL anymore?
>
Or how can a PowerPlant app use sockets?
>
>
Back to the OpenTransport glue version (CFM).
>
1. Running the old (Non-Carbon) app on my MacOS 9 machine works.
>
(Works means, it broadcasts (UDP) on port 2288 and our RIP in the local
>
subnet answers).
>
>
2. Running the old (Non-Carbon) app under classic on X works.
>
>
3. Running the new carbonized app on my MacOS 9 machine with CarbonLib
>
works also. So it seems, the glue to OpenTransport is still OK.
>
>
4. The carbonized app doesn't work on X. The UDP broadcast doesn't make
>
it to the wire.
>
>
Ideas?
>
>
>
BTW, the carbonized app can only be run native, not in the classic
>
environment. I also made a bundled app - opening the package and getting
>
info on the executable in the MacosClassic folder showed the "run in
>
classic" checkbox, but with a minus symbol, not a checkmark. Checking the
>
box and closing the dialog doesn't seem to work, when I open the info
>
dialog again, the box is not checked, but again has that minus sign. So
>
it seems my carbonized app doesn't run in the classic environment. Why?
>
>
>
>
Marc Stibane
>
Fesh! email@hidden
>
Kurf|rstenstr. 154 tel +49-30-3990 2690
>
10785 Berlin, Germany mobil +49-173-6522 422
>
>
>
In a world without walls and fences,
>
who needs windows and gates?
>
_______________________________________________
>
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.
>
--
Lyndsey D. Ferguson
Software Engineer
Nemetschek N.A., Inc.
email@hidden
--
_______________________________________________
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.