Jump to content

what is this design pattern?


Recommended Posts

i'm doing something, but i don't know what to call it. is this an accepted design pattern?

 

background:

  • i have a configuration class for my application
  • the configuration class contains paths to external (excel) files
  • you must parse out the external files and put their information back into the configuration class. i refer to this step as "parsing"
  • i'm passing the parsed configuration class over the network to an RT system, so my configuration class can't have any dependencies to non-RT stuff (e.g. Excel (ActiveX))
  • everything is dynamic dispatch so i can get some reuse out of this design pattern
post-9124-0-93674600-1387506442.png
 
explanation:
  • in this example, i have an array of configuration classes
  • all parsing functions are in methods of a "parser" class (chain link wire)
  • there is one parser class for each configuration class
  • the configuration class knows the path to the parser class

 

So, does anyone have an official name for this sort of thing? I've been referring it as "side loading". Anyone have any lessons learned on this approach? Am i running head first into any traps?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.