With the jm.pubNub Java class you can exchange messages (and entire Dictionaries) between Max patches across the Internet.
    No IP address or anything like this is necessary.
    Furthermore it is possible to exchange data with practically anything that can make http-requests (Websites direct communication with the client browser not only via the websites server), Android devices, IPhone/Pad/Pod, gaming consoles and others.
    My URL has changed. Therefore the link inside the help patch for demonstrating communication with websites is wrong. I will update the tool soon. Correct URL is: (.net NOT .de).

    • Feb 21 2012 | 2:28 pm
      Fantastic! This is an interesting approach to the next phase of internet usage...
    • Feb 21 2012 | 3:16 pm
      Thanks Stephen!
      How did you spot this so quickly - I am impresed;)
    • Jul 03 2014 | 2:40 pm
      this is an awesome tool! we were looking for an easy solution like that and i actually had given up on anything that would work that quick. thank you!
    • Jul 04 2014 | 9:05 am
      Thank You :) !
    • Jul 05 2014 | 2:06 pm
      you are most welcome! thank you for that neat tool! btw: we did test it so far mac to mac as well as mac to pc. the latter did also work just fine. did you ever think about building a handshake protocol or sth like it for that tool as? there are still drop outs that one would have to take into account. and building a handshake inside of max shouldnt be too hard but also not very elegant. just sayin in case that you plan on develop it further ;-) really love you for that one!
    • Jul 05 2014 | 2:36 pm
      Thanks for your feedback.
      the tool is basically a wrapper around the Pubnub push service. Unfortunately there is no real handshake in the concept of that service as it's purpose more to the idea of message broadcasting (and I am kind of "abusing" it for Max patch communication :) ). If you need to detect if another Max patch is present you could easily do that within your patch by sending out a "call" to the other computers/patches to wich they respond with an ID or name. A confirmation for every sent value that is successfully received is unfortunately not possible within that service;
      At the time I wrote that tool there was no way to detect connected devices directly with the pubnub API. After a long time just I re-scanned it again, and it looks like meanwhile they have implemented something like that. I like the idea to include that into the tool, but currently I do not have the time avail :(.
      --UPDATE-- Taking a closer look into it i noticed that detecting the presence of connected devices is not included in the free sandbox account of Pubnub. So it probably doesn't make too much sense to implement it....
      The dropouts are are simply due the speed of the push service (wich depends on many factors, and is usually around 250 ms). If you need to recreate "movements" within the data stream (i.e. a moving slider) you can do that with [speedlim] on the sender's side and a [line] on the receiver's side (like i did it in the help patch).
    • Apr 12 2016 | 10:38 pm
      Hey all!
      Is this open sourced somewhere?