Expert Texture Home Contact me About Subscribe Digipede Connect on LinkedIn rwandering on Twitter rwandering on FriendFeed

rwandering.net

The blogged wandering of Robert W. Anderson

Resolver One on Digipede

deatle2r1 We had a call this morning with Giles Thomas and Glenn Jones of Resolver Systems.  They demonstrated Resolver One running on the Digipede Network.

They used my IronPython Worker sample and customized the front-end Python code, leaving the C# adapter as-is.  With very little coding they had an elegant grid-enabled spreadsheet.  Try doing that with a spreadsheet or grid that isn’t based on .NET . . .

Giles said they will have support for this in Resolver One 1.5, coming out in the next couple of weeks.

Very cool. 

I’ve just installed Resolver One to take a closer look.  Already I’m impressed, but I’ll leave that for a future post.

Tags: , , , ,

IronPython and Digipede Network 2.2

. . . or IronPython-ipede (Part II).

deatle2py22I have been playing with IronPython a little.  With the release of Digipede Network 2.2, I am now able to post the sample I wrote.  It shows how to distribute IronPython objects on the Digipede Network.  You can find it on the Digipede community site.  See the posting there for details and download instructions.

The sample uses IronPython 2.0.1 and the included version of the Microsoft Dynamic Language Runtime (DLR).  While I focused on IronPython in this sample, it would be pretty easy to expand it to support other DLR-based languages.

Comments welcome.  I am specifically interested in feedback on DLR integration and initializing ScriptScope objects for each worker thread.  It seems that I should be able to do some of this only once at global scope.

By the way, one thing I like about this sample is that it shows how to keep user code completely de-coupled from the Digipede Network while still taking advantage of our deployment and payload distribution model.  This has always been supported by the Digipede Network, and this makes a good example.

Tags: , , , ,