How does it work?
MaxLink uses the MultiSender and MultiReceiver classes from Max 4.5. Messages are multicast over UDP to the local subnet using a namespace similar to OSC, and then decoded by the receiving objects.
What's it good for?
MaxLink makes it really easy to send events and data from Processing to Max/MSP to trigger any sort of audio. It's also easy to go the other way -- you can take controller data from Max and feed it to Processing to make reactive performance graphics. Using the advanced networking features, it's even possible to take inputs and outputs from various objects and virtually plug them into each other using a different computer on the subnet.
Do I have to run my Processing sketches from Max?
Nope. Each sketch can run as its own process anywhere on the local subnet.
My sketch flickers when it starts up. What's the deal?
This has to do with starting a network process in a seperate thread. Once the flickering stops, it won't happen again until you restart the sketch. This bug will be fixed in an upcoming release.
Can I download the source?
Not yet. Once I clean up the code a bit more, I'll post the source.