This article is from the Mac Programming FAQ, by Jon Watte email@example.com with numerous contributions by others.
As always, more power means more responsibility.
AppleEvents sent to applications on other Macs require authentification
the first time they are sent. If the remote Mac allows Guests to link to
programs, the INIT AutoGuest 2.0 might help (or the code solution that
comes with it and you can build into your application)
In the first version of the AppleEvent manager, there was a total 64K
limit on the size of data and overhead. This limit has been lifted with
the version of the AppleEvent manager that comes with AppleScript.
AppleEvents require a lot of memory copying and handle resizing in their
construction; this means that large AppleEvents may be slow in
construction, especially when compared to a pure PPC Toolbox or
ADSP/ASDSP link. The way around this is to use Jens Alfke's AEGizmos,
available on the Developer CD, to create AppleEvents. AEGizmos are
being integrated into System Software, so You Will be doing the right
You should use your own application signature as event class for
AppleEvents you make up, in order not to collide with anybody else.
Other than that, you are free to make your own events for your own
needs, though supporting the required events and at least a subset of
the Core event suite will buy you a lot of functinality from within
AppleScript. Especially important are the Get Current Selection and Set
Current Selection events (which are really Get/Set Data on the contents
of the current selection of the application)
The signature for your application SHOULD be registered with DTS to
avoid conflicts; this is done through e-mail to
DEVSUPPORT@AppleLink.Apple.Com and the form you use is located on the
developer CDs and found on ftp.apple.com.