On Fri, Feb 1, 2008 at 10:07 AM, dormando <[EMAIL PROTECTED]> wrote: > Tomash Brechko wrote: > > On Fri, Feb 01, 2008 at 01:30:20 -0800, dormando wrote: > >> simply to add another (standardized being a pre-req!) serialization > >> flag, so the clients don't need to even think about launching a > callback > > > > I see what you are trying to achieve: with my proposal it's either > > native or common, with your both may coexist. However, I'm more > > inclined to the solutions where the whole application agrees on one > > method, so native vs common should be mutually exclusive, and thus > > both may utilize the same hooks... > > I'm just trying to make migration easier for presently incompatible > clients. Maybe I'm not stretching my imagination hard enough to > undersatnd how this is easy. I guess they'd have to call default hooks > for native? > > ...and if you do want to mix native and cross-compatible? You'd override > the defaults and write two sets of hooks?
Hmm, I never really considered 'mixing', all I've been interested in was allowing a 'mixed set of clients' to work together in one way, not neccessarily supporting mixed clients, working in mixed ways, is that realistic? I guess Tomash' suggestion would allow someone who did want to work that way to use their own handler/transcoder/(de)serialiser to delegate between the mixed types based on something local to their application/platform ? - Ciaran
