News for hackers. Stuff that matters.

Ask HN: Why not Tar?

Most web server configurations include gzip compression to send files to the client. Wouldn't giving servers the ability to tar package cachable static files so that all those files came down in one request improve the user experience further?

Any ideas why this hasn't ever been done?

( 5 comments | on HN )
Re:Ask HN: Why not Tar? by mooism2 on Friday June 07, 2013 @01:01PM (#5840067)
Tar archives include filesystem metadata (e.g. permissions), which don't make sense if you're viewing it as a collection of cacheable resources, and omit http metadata (e.g. content types, e-tags) which it would be at least helpful to include.
Re:Ask HN: Why not Tar? by dragonwriter on Friday June 07, 2013 @12:47PM (#5839963)
> Wouldn't giving servers the ability to tar package cachable static files so that all those files came down in one request improve the user experience further?

I suspect not all that much. You'd trade request overhead for untar overhead.

Re:Ask HN: Why not Tar? by taylorbuley on Friday June 07, 2013 @12:20PM (#5839800)
Tar is an archive tool.

Gzip is compression tool.

One difference between them: an archive tool would e.g. concatenate files just once but a compression tool would compress files individually.

Re:Ask HN: Why not Tar? by zoowar on Friday June 07, 2013 @12:35PM (#5839881)
You didn't understand the question.
Re:Ask HN: Why not Tar? by forgivegod on Friday June 07, 2013 @12:18PM (#5839792)
Might be because some sites merge static files together into one resource by using custom scripts to join files, shinkansen (.net), or packtag (jsp).