Re: OSX & CFM & IPv6 ?
Re: OSX & CFM & IPv6 ?
- Subject: Re: OSX & CFM & IPv6 ?
- From: Quinn <email@hidden>
- Date: Mon, 14 Apr 2003 13:47:08 +0100
At 14:26 +0200 14/4/03, Sebastian Mecklenburg wrote:
could you explain what you mean by 'shim the interface between the
app and the plugin'?
In this context "to shim" means "to insert a shim", where "shim"
follows the dictionary, namely "A thin often tapered piece of
material, such as wood, stone, or metal, used to fill gaps, make
something level, or adjust something to fit properly." Sorry about
the wacky English.
Given that your host application only supports CFM plug-ins and the
APIs that you need to call only support Mach-O, you have to do a
transition between CFM and Mach-O somewhere. You can do this in one
of the following ways.
CFM Plug-in Mach-O Plug-in
----------- --------------
CFM app CFM app
| |
CFM plug-in CFM to Mach-O shim
CFM to Mach-O shim Mach-O plug-in
| |
Mach-O API Mach-O API
In this case I'd recommend the Mach-O plug-in approach. I'm guessing
that the CFM plug-in will be more work because you have write glue
for each API function call that you make. You will also have to do a
lot of messing around with headers. I expect that the Mach-O plug-in
will be easier because the app-to-plugin interface is smaller than
the plugin-to-system interface, and it's more under your control.
anyway, i downloaded the CallMachOFramework example. does that use
the technique you refer to?
Yes. If the plug-in interface supports callbacks, you will also need
the code from the following sample.
<
http://developer.apple.com/samplecode/Sample_Code/Runtime_Architecture/CFM_MachO_CFM.htm>
S+E
--
Quinn "The Eskimo!" <
http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware
_______________________________________________
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.