Ticket #1091 (closed enhancement: invalid)
[TiddlyWeb] generate a store that dumps to a queue
| Reported by: | cdent | Owned by: | cdent |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | tiddlyweb | Version: | |
| Severity: | low | Keywords: | |
| Cc: |
Description
It would be very useful for high performance situations to be able to return "ok" to a store.put() immediately after dropping a message into a queue.
That queue can then be processed asynchronously, probably on another process, saving the put content to multiple places.
There are lots of different things to consider with a thing like this as there are different performance and use scenarios to consider.
For example, if the put content doesn't need to be available for immediate read, it's not too hard, but if it does, then it might make sense to write the content to memcache and deliver the the memcache id to the queue. Subsequent gets read the memcache.
