-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Brion Vibber:
* Can we adapt it to a storage backend which
doesn't use a shared
filesystem?
yes, but i think it would be very silly to write such a thing for a single
extension. is the FileRepo interface generic enough to be used for something
like this? (while that would still use NFS for now, it could easily be changed
to HTTP or whatever else we decide to use in the future.)
* Garbage collection for unused output files? Previews
or changed pages
could leave the system littered with millions of output files which will
never be used again.
It'd be nice to solve these for math and timelines
as well -- perhaps a
unified system?
i'm not sure off hand how this is doable. (and it's another thing that
probably shouldn't be done inside a single extension.) but, if a mechanism
were to exist to do it, it should be simple to add to the extension.
* Rendering multiple output formats on parse could
potentially be quite
slow; if there are resource-usage problems, it would be nice to isolate
them like we currently do for image thumbnails (rendered on-demand on a
sub-cluster).
i suppose this would need something like thumb-handler.php. i will see about
adding it.
- river.
-----BEGIN PGP SIGNATURE-----
iD8DBQFJB1kGIXd7fCuc5vIRAnZBAJ4pJJFQVEdQBah3H8LebToUFQPplwCeMPBk
wmfOLL+v839KewrauIiykls=
=FbQ6
-----END PGP SIGNATURE-----