[interfacekit] Re: BHandler::fToken

>DW, Have you read the emails that Marc sent us???
Until now, I can safely say that I've only skimmed them. I just read the last 
few a little more in depth. Instead of writing e-mails, I've been writing 
code. Normally, I'm the other way around, so it felt really good to get a 
bunch of stuff checked in.

>I think he is absolutely right!
>
>We should use BHandler::fToken on app_server side! PLEASE, read Marc's
>emails to see why! BWindow::server_token will be initialized with a value
>that BWindow receives in it's constructor, and BView::server_token
>in AddChild(); a value that app_server has generated!
>
>In BWindow constructor we send BWindow::fToken, then app_server,
>does it's work and in the reply we will get a token witch we will store in
>BWindow::server_token!
<snip>
>Think about it and you will see that this is the best solution we've got so
>far.
>And, PEOPLE!, PLEASE! we have to reach a settlement!
>I think all kind of solutions have been proposed, it is time to stop
>this topic (in case of server tokens)! As Marc said, he, and me also, lost
>a lot of time reading and writing emails, instead of writing code!
Um, if I understand the way you've described it, there are *more* messages 
being sent than what I currently have in the tree. That method is worse than 
the one in place and, simply put, it's not going to happen. The current code 
in place gets a token from the server in BWindow's constructor and would (if 
it were implemented) also in AddChild.

However, if you would like to make all BWindow and BView tokens the same as 
their BHandler tokens, I have no problem with that. It'll require a couple 
changes, but nothing significant - one more attachment on BWindow side and 
one less on app_server side, which brings us back to your original question -
 accessing BHandler::fToken. Seeing how BWindow is a BLooper friend and 
BLooper is a BHandler friend, couldn't we just implement a BLooper::GetToken 
private function and not break BC? The server doesn't care what actual value 
is used as long as it's unique. This would avoid everyone and their brother 
being a BHandler friend class and we could still access the necessary tokens 
when we need them. Erik?

--DW

Other related posts: