The drivers try to map BSON types to driver specific native types,
while still providing flexibility to the developer. The encode/decode
hooks work at a low level within the driver, at the wire protocol
level. This gives you some latitude, but the transformation will be
applied across all objects targeted by the hook. Identifying and
modifying more sophisticated objects and structures by name will be
easier to do in your application once the DBObject has been created.
On Apr 19, 2:26 pm, Bilal Clarance <bclara...@gmail.com> wrote: