However the specific immediate use of Max4Live I have in mind for use within Ableton Live only will require use of one or more of the following types of objects:
tcp send/recv udp send/recv or serial io, or exernal objects implemented by myself in C++ (which depends upon which approach will yield what I need).
On the surface it looks like all of these should function given the stated limitations, however I dont want to be stuck down the line having paid for Max4Live then discovering in about 30 days time that actually I have wasted my money and should instead have just written VST plugins directly in C++ because non of these objects are uported by M4L on its own - quite simply, right now aint a great time to be spending money that I can pospone for a month or two.
I will buy Max4Live eventually anyway for its audio capabilities etc, however right at this point in time I have a far more urgent need of enabling Live to communicate some automation paremeters from live clips to another application runing on the same or another computer. Max4Live seems to be a way of drastically spending up this dev process (compare to writing VST plugins and UIs for them etc to meet my current needs).