Why was this implementation chosen, at least on the front-end if not on the back-end as well? I understand that files in a user's History are currently contained as a blob in a database (correct?). Does this have an advantage over simply storing it as plain files in a user-directory created by Galaxy? Is there any plan to implement a "directory view" on the front-end to manage history files easier when the history grows very large?
In the context of my own use cases, a lot of our current pipelines are very 'file-oriented', so the prospect of trying to get them implemented in Galaxy seems a little daunting.