The problem I have is that I need to do about 40+ conversions to convert loosely typed info into strongly typed info stored in db, xml file, etc.
I’m plan to tag each type with a tuple i.e. a transformational form like this:
host.name.string:host.dotquad.string
which will offer a conversion from the input to an output form. For example, the name stored in the host field of type string, the input is converted into a dotquad notation of type string and stored back into host field. More complex conversions may need several steps, with each step being accomplished by a method call, hence method chaining.
Examining further the example above, the tuple ‘host.name.string’ with the field host of name http://www.domain.com. A DNS lookup is done to covert domain name to IP address. Another method is applied to change the type returned by the DNS lookup into the internal type of dotquad of type string. For this transformation, there is 4 seperate methods called to convert from one tuple into another. Some other conversions may require more steps.
Ideally I would like an small example of how method chains are constructed at runtime. Development time method chaining is relatively trivial, but would require pages and pages of code to cover all possibilites, with 40+ conversions.
One way I thought of doing is, is parsing the tuples at startup, and writing the chains out to an assembly, compiling it, then using reflection to load/access. Its would be really ugly and negate the performance increases i’m hoping to gain.
I’m using Mono, so no C# 4.0
Any help would be appreciated.
Bob.
Here is a quick and dirty solution using LINQ Expressions. You have indicated that you want C# 2.0, this is 3.5, but it does run on Mono 2.6. The method chaining is a bit hacky as i didn’t exactly know how your version works, so you might need to tweak the expression code to suit.
The real magic really happens in the
Chainerclass, which takes a collection of strings, which represent theMethodChainsubclass. Take a collection like this:This will generate a chain like this:
Chainer.CreateChainwill return a lambda that callsMethodChain.Execute(). BecauseChainer.CreateChainuses a bit of reflection, it’s slow, but it only needs to run once for each expression chain. The execution of the lambda is nearly as fast as calling actual code.Hope you can fit this into your architecture.