From: Matthew T. <ma...@tr...> - 2003-06-12 15:29:10
|
I'm thinking about building a request broker/message queueing system, and have been intending from day one to do anal serialisation of message data so nothing will be lost if the machine goes down etc. I spent far, far too long trying to persuade XML to be my transport layer, and threw away a couple of semi-working parsers that were just too evil to carry on with. The request structure is simply streams of requests with an action associated with them - usually 'parallelise' or 'serialise', and nest. The contents of the request simply indicates a destination and is 'just data' I'm now intending to use YAML as the underlying storage, but wondered if anybody had any suggestions for using it for this task - i.e. creating effectively a transaction log for a tree structure (LDIF-like) and periodically dumping the entire tree as a reference position and to speed restarts. There was mention of document node change serialisation, but I'm unsure whether that would optimally be done the same way (colour me green on the subject) -- Bring me my etherkiller; Oh clouds unfold! / Bring me the magic smoke of desire I shall not cease from mental fight / Nor shall my LART rest in my hand Till we have buried the bodies / Of all the lusers in all this land -- rpg, ASR [ My homepage is http://www.trout.me.uk/ ] |