Quote:
Originally Posted by theducks
1) Big (write) Security issues would need to be solved.
2) This is not as simple a task as you make it. any change a is a 'Transaction' a) DB Metadata change. b)1 or more Book format files written/changed. 3)Backup metadata written. (there might be more, I am not a Calibre developer)
To steal Kovid's line  'Patches are welcome' |
What about using a subset of CMIS?
Seriously, it's pure madness when you go to multiple computers and need to read a book or modify one, calibre-server doesn't support writing so the process is messy if you are remote (right?). What about an interoperatibility standard for ebook libraries?
A multi-user library server for Calibre could be useful, if it's strong enough and adopted as standard, ebook readers and other ebook managers could implement it.
You are right about patches, but I'm not so used to Python. I think Calibre must be improved in resource efficiency first, currently it's damn slow.