Now that DS runs an actual webserver to handle the embedded interface html windows, we could make output and browse_rsc much less of a pain if the the client webserver just waited for the image/js/css to come down the pipeline if its queued for sending, before serving it up, rather than serve a 404.

Might require some protocol changes, i don't know if clients know about files pending in the browse/browse_rsc() queue.