>When an MCCISendOutput is done for a particular MIME type is the expected
>behavior that Mosaic will both display AND return the document specified in
>the MCCIGet call for an item of that type? More specifically, there are 4
>possibilities for how the program might like Mosaic to respond:
>
> 1. Display the document and send a copy to the application.
> 2. Display the document and DON'T send a copy to the application
> 3. DON'T display the document, but send a copy to the application
> 4. And NEITHER display NOR send the document to the application.
>
>I thought that 2 meant SendOutput was NOT turned on, 3 meant that it was
>turned on, 4 meant it was not turned on and you did a Get with OUTPUT_NONE,
>and that 1 wasn't implemented. If this summary is incorrect then I would like
>to report a bug :-) . Could you please give the combinations of SendOutput and
>Get that achieve the above 4 results?
I'll do my best :-)
- Display the document and send a copy to the
application.
-
MCCIConnect
-
MCCISendOutput with
the
appropriate MIME type
-
MCCIGet with an output of
either MCCI_DEFAULT, MCCI_OUTPUT_NEW, or
MCCI_OUTPUT_CURRENT
-
MCCISendOutputStop
-
MCCIDisconnect
- Display the document and DON'T send a copy to the
application.
-
MCCIConnect
-
MCCIGet with an output of
either MCCI_DEFAULT, MCCI_OUTPUT_NEW, or
MCCI_OUTPUT_CURRENT
-
MCCIDisconnect
- DON'T display the document, but send a copy to the
application
-
MCCIConnect
-
MCCISendOutput with
the
appropriate MIME type
-
MCCIGet with an output of
MCCI_OUTPUT_NONE
-
MCCISendOutputStop
-
MCCIDisconnect
- And NEITHER display NOR send the document to the
application
-
MCCIConnect
-
MCCIGet with an output of
MCCI_OUTPUT_NONE
-
MCCIDisconnect
Unfortunately since the OUTPUT NONE request is not yet
implemented by Mosaic (at least thats what it prints out when I try it
:-) (3) and (4) will not work yet.
Adrian
|
It depends (I think) 
