The reason I opted for /view/ instead of /download/ is that its header for
/download/ is
Content-Type: application/octet-stream
whereas with /view/ it is
Content-Type: text/plain;charset=UTF-8
This makes sense, as "download" initiates in the browser exactly that -- a
download (save to file). Whereas Jmol just needs to view it. It seemed
safer to me to pull it in as a text file than a byte stream.
Could be wrong about that.
Bob
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
