Blarg. I can start looking into this after I wrap up my
BArchivable-related work.
e
DarkWyrm wrote:
>
> >Huh. I thought BRoster *used* the registrar. Maybe we could ping
> >George and the happy folks on BeDevTalk to get a definitive answer?
> I contacted him - a BRoster class instance contacts the registrar.
>
> There are a lot of things he can't legally tell us, so we're stuck with
> general stuff. According to the Be Book, the constructor establishes a
> connection with the registrar. I'd bet that setup for that kind of thing is
> similar to that of the BApplication constructor and the app_server. I took a
> quick peek at the BRoster header and I think that the most reversing work
> that we need to do will be on the registrar itself and the BRoster class.
> Ugh.
>
> --DW
