> I don't see the difference between MCCIPoll
>and MCCIIsThereInput. Both tell you if there is
>incomming input.
MCCIIsThereInput just informs you whether there is input
pending, while MCCIPoll actually processes the input, calling any
appropriate callbacks.
> Also, where would you use MCCIGetSocketDescriptor?
When you wanted to use the raw protocol rather than the API.
> There's not enough in depth documentation on
>CCI. Anyone thought of writing up some detailed information?
Do you mean the documentation for the protocol or the API? I have to admit
I don't think the current documentation is all that bad. What aspects are you
finding difficult to understand?
> Would you generally keep the connection open for
>the duration of the application. Or would you make the
>connection, tell mosaic what to do, then disconnect. Then
>open another connection the next time you need to control
>mosaic?
This, I think, would depend on what you wanted to do. If my application was
only controlling Mosaic for brief periods of time during its execution I would
probably open/close connections. If my application was continually exchanging
information with the browser I would keep the connection open.
Adrian
| 
Re: MCCIPoll and MCCIIsThereInput 
