I kind of like this approach... I can see where it also provide some
flexibility as we go forward. Possibly even, dynamically building the
language packages from something like Drupal's translation manager that
was created in the last SoC.
Definitely not something we want to squeeze into R2.3. Maybe we should
start a R2.4 wish list :-)
Andy Staudacher wrote:
> Some feedback for your design doc from
> Instead of building static cross-plugin language package files, how about
> using HTTP multipart responses?
> So the client requests packages a,b,c,d and the DP server responds with a
> single multipart response, concatenating the packages in a single response.
> Required changes:
> - The HTTP client (or just the DP client) in G2 would need to be improved to
> process multipart responses.
> - The DP server is no longer just a file server. There's a frontend script
> that handles requests (valide inputs, building HTTP response by streaming
> files from fs and printing them to the output).
> * The advantage would be that we wouldn't have to build aggregate language
> files, no need for a new kind of DP index/package.
> * And the downloads would always be efficient since the aggregate file that
> is sent back is exactly what has been requested, not more, not less.
> * No changes to packaging/release/DP cron scripts.
> * Can be reused for any DP package downloads, not just for language
> * New code required. The code for your design doc is almost ready.
> * The load of the DP server will go up a bit, but the DP volume isn't that
> big yet.
> * Unexpected repercussions :)
> - Andy