[interfacekit] Re: First whack at a schedule

Ah, OK; sounds like the registrar is sort of a server itself.  
Interesting ...  Now if we can just figure out how the dang thing works, 
we'll be in like Flint.

e

>>OK, so a little digging and I've come to the conclusion you're talking
>>about the MIME registrar.  Talk about your undocumented no-man's land. 

>>Isn't this something the Storage Kit folks (are there any of those?)
>>should be taking care of?  Just checked; there *isn't* as Storage Kit
>>team. *~sigh~*
>>
>>Alrighty then guys, unless a Storage Kit team materializes, we're 
going
>>to have to implement the MIME registrar and related Storage Kit
>>classes.  Wee.
>>
>>I'll contact Michael Phipps and see if he knows anything different 
about
>>the situation.
>>
>>e
>Excerpt from an e-mail from George Hoffman:
>
>> Anyway, does the
>> registrar get most of its info from the kernel or the app_server?
>
>The registrar, like the app_server, gets contacted directly by threads 
that
>want to use it's services.  It does not talk to the app_server at all.
>
>> Also, I
>> know the app_server thread handles new application setup, but are
>> you able to
>> tell me whether the request for the new app goes to the registrar or 
the
>> app_server?
>
>The BApplication constructor contacts both the app_server and the 
registrar.
>The app_server deals with all input and graphics related tasks, while 
the
>registrar is used for publishing info about running apps, broadcasting
>messages, launching apps that deal with a particular MIME type, etc.
>
> BTW, for future reference, what kinds of questions
>> would wou be
>> able to answer?
>
>Nothing we wouldn't put in a newsletter.
>
>Mostly undocumented, but we have help. :)
>
>--DW

Data is not information, and information is not knowledge: knowledge is 
not understanding, and understanding is not wisdom.
        - Philip Adams

Other related posts: