Hi Martin, I rather think no one bothered yet to call a simple Callback a Design Pattern. If you wish, you may use it by this name - but it's really not a Xerces-specific thing. Implementing GUI Frameworks withou callbacks would be - rather interesting...
Or, if it is more elaborate, like implementing a whole behaviour of a specific subsystem with the help of a derived class - well, that's Specialising by Deriving, nothing genuine again. Again, I guess this is so typical for OO-Frameworks, that probably no one ever thought about calling it a Design Pattern (although you may regard it as one, as it fits to the definition). Did you check the POSA-Books, too? I really think, both methods simply are not complicated enough to warrant it a description in a Design Pattern book. The GoF-Book was pretty full anyway... :) Best regards, Denny ----- Original Message ----- From: "Martin Bosticky" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 27, 2004 1:28 PM Subject: A design pattern in xerces-c? > Hi > > In xerces, applications using DOM implementation can derive a class from > DOMErrorHandler and supply that class to xerces to handle errors. I am > wondering if there is a desing pattern that describes this solution? If so, > does it have a name? > > I had a look arround and the closest design patterns i found were Visitor > and Proxy from the "Design Patterns..." by Gamma, Helm, Johnson and > Vlissides. But none of these two are really appropriate i think. Why isn't a > callback a design pattern? Am i going mad? Are xerces developers using > design pattersn and do they know they are? > > Martin. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
