Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: MongoDB
-
Labels:None
Description
Right now there is code that can convert between a FudgeMsg and a MongoDB BasicDBObject, so that you can persist and load Fudge messages in MongoDB.
However, given how similar they are, it should be possible to write support for the MongoDB protocol itself with Fudge messages, so that you don't have to do a message structure copy/convert in order to integrate with MongoDB.
We need to be clever about how we handle this kind of thing - so far we've got at least four possible implementations of FudgeMsg:
Doing this through the context makes obvious sense when reading from a stream, but I've an uneasy feeling there's more to it than that...
- Simple, as current
- Lazy unpacking of fields
- MongoDB-compatible
- One that tracks which fields you've read (needed to support evolvability in serialisation)
Doing this through the context makes obvious sense when reading from a stream, but I've an uneasy feeling there's more to it than that...