wowserhq/pipeline

Client asset server for Wowser

pipeline's Issues

Investigate HTTP2

Per @timkurvers:

Should in theory increase performance.

Given the sheer quantity of files needed to render a scene, it'd be helpful if the pipeline server wasn't stuck in the HTTP 1.1 era.

Support multiple builds

Since it's handy to be able to see how a particular asset worked in a particular version of the game, it'd be lovely if the pipeline server supported configuring more than one build.

Something like this:

• /pipeline/12340/DBFilesClient/AreaTable.dbc.json
• /pipeline/20253/DBFilesClient/AreaTable.dbc.json

Migrate pipeline server out of main wowser repo

Currently, a bunch of concerns all live together in the main wowser repo. This includes the pipeline server, which is slated to move to this repo. Let's make it happen!

Support CASC

Since versions of World of Warcraft after Mists of Pandaria use CASC as their storage format, we should add support for CASC to the pipeline server.

https://github.com/ladislav-zezula/CascLib would fit the bill rather nicely, I think.

Add Windows CI via AppVeyor

Similar to #6, since wowser aims to work on Windows, we should be testing builds of wowser-pipeline on Windows. AppVeyor seems to be the popular CI service for Windows projects, and, like Travis, allows open source projects to build for free.

Add macOS CI via Travis

Since wowser officially supports macOS, we really ought to be testing wowser-pipeline on macOS. Fortunately, Travis supports macOS, so this should just be a matter of getting the config right (knock on wood).

Support CORS

In order to support clients operating on different ports or even different domains, devising a CORS mechanism for the pipeline server seems like a good idea.