> >So, what would the world think of reserving 174 to
> >be blr_user_id. That would take a single blr argument
> >which would be one of the set
> >
> > blr_user_transaction
> > blr_user_connection
> > blr_user_role
> > ...
> >
> >where ... would expand as necessary.
> >
>
> Yeah. Although the Interbase role model is a single role
> identified at logon, a more useful model is multiple roles,
> each of which may be turned on or off during a session.
> Although I don't think this is the most critical short term
> feature on the menu, designing an interface that couldn't
> support it could be a problem down the road.

Perhaps you could simply return the list of ROLE(s) being used in a
delimited string of some kind. It is just a string of characters afterall.

What would user_transaction and user_connection return?

For my purposes (event driven auto synchronization of datasets on clients) I
only need to know that certain changes were committed via another connection
and not the current one. A unique ID of some sort is all I need.

Having the transaction would also be useful.

Thanks for bringing this up. It could help me out a lot, not to mention
thousands of others who use features in IBO that would reap immediate
benefits from this.

Regards,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com