Using plugboards with content server

GRiker · 02-18-2011, 04:58 PM

I'm interested in the possibility of using plugboard transforms inline with the content server.

Is this feasible?

G

chaley · 02-18-2011, 05:09 PM

Yes, but with caveats.

There are two kinds of plugboards. The first affects copying to a device, changing metadata during the copy process. The second affects databases stored on the device (device_db). The content server could use only the first.

Looking at the content server code, I see that metadata is updated only for EPUB files (library.server.content.py). Today it does not use any plugboard. If a device 'content_server' is added to plugboards, and if content.py is told to use that device, then plugboard transforms would be applied. The code would look a lot like that found in gui2.device._upload_books.

One concern is that today, no other format would acceptable as a plugboard source for the content server. Should the plugboard code be told about that? Hard to say. The current code permits specifying source formats that don't support certain metadata transforms, so the easy answer is 'no, and let the destination do what it can.' However, I can see problems with that answer.

GRiker · 02-18-2011, 05:27 PM

My use case is ePubs on iDevices, so it sounds like it could work.

Would it be reasonable to only enable epub as valid transform destination for the content_server device, and deal with other formats as they are requested?

G

chaley · 02-18-2011, 06:04 PM

Quote:

Originally Posted by GRiker

Would it be reasonable to only enable epub as valid transform destination for the content_server device, and deal with other formats as they are requested?

The problem is that there is no mechanism in place in plugboard setup to restrict the formats a device can handle. Any restriction would be adhoc. Perhaps that is OK in this case.

kovidgoyal · 02-18-2011, 06:11 PM

It should be possible to have the metadata written to MOBI files as well as EPUB in the CS (MOBI is a little slower than EPUB which is why it was left out originally). That covers the two most common formats, IMO we can ignore the rest.

02-18-2011, 04:58 PM	#1
GRiker Comparer of the Ephemeris Posts: 1,496 Karma: 424697 Join Date: Mar 2009 Device: iPad	Using plugboards with content server I'm interested in the possibility of using plugboard transforms inline with the content server. Is this feasible? G

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
content server error	brysio	Calibre	3	12-18-2010 01:24 PM
Need help - content server	Sydney's Mom	Calibre	0	08-28-2010 05:07 PM
Content Server edit help	selfdestroyer	Calibre	2	08-06-2010 05:47 AM
Web Content Server	mezme	Calibre	7	01-08-2010 10:59 PM
Content Server	thibaulthalpern	Calibre	5	04-28-2009 01:56 PM

02-18-2011, 05:09 PM	#2
chaley Grand Sorcerer Posts: 12,029 Karma: 7257323 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	Yes, but with caveats. There are two kinds of plugboards. The first affects copying to a device, changing metadata during the copy process. The second affects databases stored on the device (device_db). The content server could use only the first. Looking at the content server code, I see that metadata is updated only for EPUB files (library.server.content.py). Today it does not use any plugboard. If a device 'content_server' is added to plugboards, and if content.py is told to use that device, then plugboard transforms would be applied. The code would look a lot like that found in gui2.device._upload_books. One concern is that today, no other format would acceptable as a plugboard source for the content server. Should the plugboard code be told about that? Hard to say. The current code permits specifying source formats that don't support certain metadata transforms, so the easy answer is 'no, and let the destination do what it can.' However, I can see problems with that answer.

02-18-2011, 05:27 PM	#3
GRiker Comparer of the Ephemeris Posts: 1,496 Karma: 424697 Join Date: Mar 2009 Device: iPad	My use case is ePubs on iDevices, so it sounds like it could work. Would it be reasonable to only enable epub as valid transform destination for the content_server device, and deal with other formats as they are requested? G

02-18-2011, 06:11 PM	#5
kovidgoyal creator of calibre Posts: 44,542 Karma: 24495948 Join Date: Oct 2006 Location: Mumbai, India Device: Various	It should be possible to have the metadata written to MOBI files as well as EPUB in the CS (MOBI is a little slower than EPUB which is why it was left out originally). That covers the two most common formats, IMO we can ignore the rest.

Advert

Advert