best list / enum driven slight job system
consider i'm interfacing an outmost component send summary (db table, summary queue, web service) format. "message header" there "messagetype" array 1 20. messagetype defines rest message. there things new, modified, deleted, canceled...
my initial desire setup an bulletin interpretation types. following parse array an enum type. an enum i setup customary switch box component sole slight any summary types.
one large pleasantness maintenance.
a switch / box component massive teadious but, it's unequivocally simple.
various list / settlement systems challenging someone else grok supplement new messages tweak existent messages.
for 12 messagetypes switch/case component seems definitely reasonable. reasonable cut-off indicate switch list driven system?
what kinds systems deliberate best doing forms problems?
i'm sourroundings add-on both c# java here since it's definitly common problem. there languages same issue.
Comments
Post a Comment