User Spaces

[Joel Cochran <jrc@xxxxxxxxxx>]

Along the lines of the recent thread regarding DataQueues, I'm trying to
determine whether or not to use User Spaces for a particular project. 
They sound intriguing, but having never used them before I'm not sure if
they are correct for this application:

For a new application we are writing there will be a security
configuration file.  Each user will have authorities set at the option
and function key level.  Naturally this is all DB driven, but in essence
each authority gets verified at three differenct levels.  At screen
display time to determine whether or not to display an option; at option
processing time to verify that the user did not select an unauthorized
option, and at processing time to make sure that no back doors were
taken in getting there.

Given that this processing will need to take place for every screen,
selection, and processing, it appears to me that this may be overly
burdensome on the DB.  So to bring this back to User Spaces, I'm
wondering if it would be better for us to read the authorities in once
when the user signs into the application, store them in a User Space
unique to that log in, and then access the user space for the
verification instead of the DB.  I'd probably create the User Space in
QTEMP so that the GC is taken care of automatically.

Would this be faster, better, etc, or am I making a mountain out of a
mole hill?

Thanks,

Joel
http://www.rpgnext.com