[interfacekit] Re: Server Tasks
- From: DarkWyrm <bpmagic@xxxxxxxxxxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Thu, 18 Oct 2001 20:24:22 -0400
>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
- Follow-Ups:
- [interfacekit] Re: Server Tasks
- From: Erik Jakowatz
- [interfacekit] One-thread-per-window
- From: DarkWyrm
- References:
- [interfacekit] Re: Server Tasks
- From: Erik Jakowatz
Other related posts:
- » [interfacekit] Server Tasks
- » [interfacekit] Re: Server Tasks
- » [interfacekit] Re: Server Tasks
- » [interfacekit] Re: Server Tasks
- » [interfacekit] Re: Server Tasks
- » [interfacekit] Re: Server Tasks
- [interfacekit] Re: Server Tasks
- From: Erik Jakowatz
- [interfacekit] One-thread-per-window
- From: DarkWyrm
- [interfacekit] Re: Server Tasks
- From: Erik Jakowatz