Much ado about scripting, Linux & Eclipse: card subject to change

Showing posts with label mdd. Show all posts
Showing posts with label mdd. Show all posts

2007-12-12

Beer-to-Peer Networking, Part 1

The following is an experiment in B2P networking, and an attempt to implement a cross-province UUBP transfer. (Aside: I had considered a cross-country experiment too, eg., Toronto to Porland, but I'm not sure how to implement such an idea, especially given the ever-tighter security policies at the US-Canada border. Any suggestions?)

I'd also like to say upfront that this experiment should not be construed as an irresponsible attempt to encourage others to mix beer (or any form of alcohol, really) w/ software development. Drinking and coding can lead to serious problems. Please, B2P responsibly.

While I realize I'm deviating from the spec, I've decided to implement using a more MDD-based approach, in that the message I plan to send via UUBP will not be an actual beer, but rather a model of a beer, which can then be extrapolated and ingested (and later digested!) at the receiving end.

Raw materials can be acquired from your nearest Beer Store and your office's mail room.


Required Materials

Next, the message is encapsulated for security using the "gift envelope" technique, which I presume won't cause licensing headaches or adoption problems as this technique is already widely used in the public domain.


Assembling the Inner Packet


Completed Inner Packet

Now, a second layer of encapsulation is required to ensure the packet can be properly delivered to its intended audience. While there is no real protection of malicious packet sniffing, this at least ensures that the casual observer won't want to intercept the packet. The procedure is very similar to the above, and so will be lest as an exercise for the reader.

With the completed packet, it was time to attempt delivery. The UUBP spec says nothing about transport methods, so I'll first try a web-based approach:


First Delivery Attempt

Unfortunately, even with a 20" monitor, the packet is too large to be sent via the web:


Delivery Attempt Failure

After this initial setback, it was decided to try a more conventional delivery mechanism. This Canada Post node will be employed to transfer the completed packet to its destination.


Second Delivery Attempt: Success!

The UUBP packet is now in transit via the B2P network. With any luck, its recipient will receive it in a couple of days and take some shots, er, photos to complete Part 2.

UPDATE: See Part 2.

2007-11-03

Lies, damned lies, and a side order of acronym soup

By my calculations, EMF has scored over 2 million download requests since 2006-01-01. That's a huge number, but it's also an inaccurate number because our stats gen was broken for a while so there's a big hole in the Update Manager download stats. As such it's probably much higher, given the traffic we've had since the stats tool was fixed.

Looking at the overall numbers for all the tracked Modeling projects, we've had 5 million download requests since 2006-01-01 for EMF + M2T + MDT ... and that's just the Update Manager requests!

It's also fun to see who's downloading our bits. As expected, the US tops the chart, with Canada a respectable 8th. To get a sense for where EMF is used consider where the following projects are developed:

  1. US: GMF, M2T-JET, WTP, TPTP, VE, ...
  2. China: MDT-EODM, TPTP
  3. France: EMFT, MDDi, M2M, GMT
  4. Canada: EMF & EMF-QTV, MDT (UML2 & OCL), M2T-JET, GEF, GMF, WTP, TPTP, ...
  5. The Netherlands: EMFT-Teneo
  6. Czech Republic: GMF, MDT-UML2 Tools

To paraphrase Ed and the Zulu people, "umuntu ngumuntu MDD!" ;-)