Users and their roles

[dacosta1427]

Hi Blake,

Kudos on the KISS Framework, it brings me back to the days of (Apache) Tapestry 3.X. Nice and elegant, no fluff and nonsense. Very inviting to invest some time into learning it (by doing obviously).

Since a system without users is fairly senseless, the authentication incorporation makes a lot of sense to me.
However, though I appreciate the way it is shipped I do wonder what would be the best way/location (in the code) to incorporate a more extended form of user(mgt)?
I already written have a pretty sophisticated Actor (read entity that is 'doing' something in/with the system) Mgt component/ suite that I would like to add to the code but I'm a bit reluctant because I don't want to add it in the wrong fashion.

Question 2 pertains to something that would make a lot of sense (imho) as well and that would be including an object db to the suite of DBs already supported. This may however be a better subject to talk about off-board.

Hopefully you can supply me with a reply on the 1st Q at least ;-)

Cheers,
Fermin

[blakemcbride]

Hello Fermin,

Thanks for the feedback and kind remarks!

In terms of user data, I understand. I had the same problem in another system I built with Kiss. I don't remember exactly how I solved it (whether it was generic or application-specific). I agree, a generic solution is needed. I'll look into it and get back to you within a few days.

I am reluctant to use Actor because I don't want to add a bunch more dependencies unless it is really warranted. Off the cuff, I'd think it would be easy to address in straightforward Java. We can discuss this and give it more thought.

With regard to the object database, while I've used one once in the past, I generally don't use an object database—hence the shortcoming. I don't think it makes sense for me to enhance the current SQL API because they're so different. A new API should be written. We can work together on this.

Also, while this discussion list is a great place to get things like this started, you may want to use my email address for longer discussions.

Thanks again!

Blake

[blake@mcbridemail.com]

[dacosta1427]

Hello Blake,
Thank you for the swift reply.
I understand fully what you say. I'm always looking for generic and elegant solutions because i know, from hard experience, that if one goes the complex route headaches are bound to follow.

Will contact you you on the direct mail.

Cheers,
Fermin

[blakemcbride]

Hi Fermin,

Look at the login() method in the file src/main/backend/Login.groovy
It has two commented-out lines.
The first line shows how to associate user-specific data on the back-end.
Anything added with the putUserData() method is accessible by all future web services and is specific to
that particular user.
The second line adds user-specific data that gets sent to the front-end. From that point, front-end user-specific-data
should be cached by the front-end.

Each web service is passed an argument named "servlet". servlet.getUserData("abc") can be used to retrieve that user-specific data
that was established at login time. Additionally, web methods may add or change that data too.

This is documented in section 4.2.3 of the user manual.

With regard to the object database, it is my understanding that each object database has its own API. There is no JDBC for object databases. Which object database are you interested in? (Although I have to say, I am reluctant to add features that add additional required dependencies but am happy to add features that don't.)

I hope that answers your question.

--blake