[interfacekit] Registrar

>
>> I'd like to to work on BRoster.  Also, can somebody shoot me reply?  I 
sent
>> a few messages out 2 weeks ago trying to confirm, but they didn't show up.
>> I did recently change my mail server though, so could be that.  Anyway, 
let
>> me know if that's still open and I'll get to work.  Thanks...
>
>Do we need to have a working registrar(? app_server?) to get BRoster up
>and running?
>
>Isaac
Speaking mostly from conjecture, I suspect that we will need a working 
registrar in order to get BRoster going. The main reason I say this is 
because the API appears to be mostly wrappers for covering up communications 
with the registrar. We are both lucky and not lucky that the registrar is 
pretty much a black box - very little is mentioned in the Be newsletters or 
the Be Book about the thing, which means that we can more than likely design 
our own protocol for the thing. I've had to look into some stuff it does in 
order to figure out what the app_server does NOT do.

Reversing it, as Erik suggested, may not be necessary, but having looked at a 
symbol table dump I think there are quite a few good nuggets of info in 
there. It may be possible to have two registrars play nice-nice while running 
concurrently - ours and Be's - in a way similar to how the two app_servers 
can coexist.

--DW

Other related posts: