* Trey Harris ([EMAIL PROTECTED]) [050426 03:34]: > There's a design pattern whose name I'm having trouble remembering (which > is making it hard for me to look up any literature on it). I'm hoping > maybe someone here can help me. > > I thought it was called the "recognizer" pattern, but Googling isn't > turning up anything by that name. Basically, you have a data blob, and a > list of candidate classes, and you throw the data at the classes one by > one until one of them "recognizes" the blob and returns an object > encapsulating it. > > In more advanced usage, you get responses back from the candidate classes > about how well they recognize the blob, and you eventually use the class > that can best recognize it, even if several can recognize it to some > extent.
It sounds like a Chain of Responsibility (list of candidates + throwing the data at them) implementing a Factory (passing in some generic data and getting back an appropriate object). Chris -- Chris Winters (http://www.cwinters.com) Building enterprise-capable snack solutions since 1988 _______________________________________________ sw-design mailing list [email protected] http://metaperl.com/cgi-bin/mailman/listinfo/sw-design
