> > >>PS: Does anyone know how to get the port id and token from a > BMessenger. > >> For the BQuery implementation I used a pretty dirty hack. I > > > guess, > it > >> must have to do something with the friend class =5FTRoster=5F. > >There isn't a way for us to access Be's BMessenger tokens AFAIK. > > Then > again, > >Erik knows way more about tokenspace stuff than I do. Ports for > > classes > are > > Only because I pretty basically made it all up. ;P Seriously though, > TokenSpace.h (which is an app kit private header) defines the > facility > for creating and keeping track of BHandler tokens. Currently, you > can't > do a reverse-lookup, but that would be trivial to add. Even for BHandlers in other applications=3F I thought the token space was application local. > I'm curious > though; why do you need this information=3F Can't you just send the > notification via the BMessenger itself=3F No, not the BQuery object sends the notification messages, but the kernel (the vnode layer supposedly). To open a live query we have to use: DIR *fs=5Fopen=5Flive=5Fquery(dev=5Ft device, const char *query, uint32 flags, port=5Fid port, int32 token); CU, Ingo