|
I notice that there is no support for the DISPLAY request in the
CCI
API. Its future also looks quite bleak from the comments in the CCI Protocol Spec.
This worries me since it strikes me as darn useful. Currently the only
mechanism in the API which we can use to get Mosaic to display something is a
call to MCCIGet with a URL. This has two problems:
- We have to mess around finding the appropriate extension for the MIME
type we want to display. If we want to do this properly it will mean
mucking around with the users
mime.types file.
- We have to have access to either:
- An HTTP/FTP/... server that the Mosaic process can access
- The local filespace the Mosaic process is on
Neither of which may be available.
The problem cited in the CCI Spec of:
Note 1: In order to have a valid URL associated with this document
which the browser needs, the browser will be need to save
it as a local file. ick! This request is on the verge
of being deleted. bonk
Does not seem that major a hassle to me.... so why no support in the API? Just
lack of time?
(It looks like the raw code for DISPLAY is in Mosaic, but I
haven't tried it yet since I hoped to avoid all that tedious mucking around
with sockets by using the API :-)
Adrian
| 
No support for DISPLAY in API? 
