Chris, I think the solution is very simple.
You just need to make sure that the HTTP header sent in the response from the server states the proper MIME type for LDRAW files. The element you need to send back to the client is
the "Content-Type" field in the HTTP response header.
The user can then associate a tool with that MIME type.
As "LDRAW" is of course not part of the official MIME standard, we need to use the "x-" prefix for unofficial file types.
Probably
application/x-ldraw
or
model/x-ldraw
would be something good IMHO.
Alternatively, you could make the URL "appear" as an *.ldr file (instead of *.cgi), so users might,
alternatively to the MIME type, use their normal file associations for opening the result file.
Since the result - as far as I can see - is a mix of both the old and the new version of the file,
probably either *.mpd or *.ldr would be a good file extension to pick; not *.dat
You just need to make sure that the HTTP header sent in the response from the server states the proper MIME type for LDRAW files. The element you need to send back to the client is
the "Content-Type" field in the HTTP response header.
The user can then associate a tool with that MIME type.
As "LDRAW" is of course not part of the official MIME standard, we need to use the "x-" prefix for unofficial file types.
Probably
application/x-ldraw
or
model/x-ldraw
would be something good IMHO.
Alternatively, you could make the URL "appear" as an *.ldr file (instead of *.cgi), so users might,
alternatively to the MIME type, use their normal file associations for opening the result file.
Since the result - as far as I can see - is a mix of both the old and the new version of the file,
probably either *.mpd or *.ldr would be a good file extension to pick; not *.dat