add companyid

[transmeta01]

Hi Cristian,

there should a companyid in all DAO. This companyid allows to
discriminate everything based on a companyid. I know this will change
the relational model a little bit. Let me know what you think about
it.

regards
Richard

[Cristian Olaru]

Hi Richard.

This is unclear for me. You want the application to be multitenant? See http://en.wikipedia.org/wiki/Multitenancy
I think this can be done simple using AOP in background. I see something like this in: http://www.grails.org/plugin/multi-tenant (Spring used in background)

Otherwise I don't understand the use of this dis discriminator.

Regards...

--
Cristian Olaru
weblog: http://olaru.blogspot.com
mobile: 0743163039

[Richard Mutezintare]

Yes the application needs to accommodate multiple tenants.

Richard

sent from android 2.2

[transmeta01]

HI Cristian,

I pulled your commit and quickly ran through it. Very excellent work!
The jetty plugin is a very good idea.

The resource code is still very embryonic. For instance, no location
(after creation of the new resource "user") is set for the creation of
new user (newly registered user). I will fix that. The design is still
in progress.

Security considerations:
Also on http://scrumy.com/classic, I posted a task that requires the
use of a table that links user_id, and contains a the password
salt....it is used to get the salt for the user password. When the
user registers, his/her password is salted (the salt maybe MD5 or
SHA-1 hashed) that is saved in the "sec" table. This table is then
used to un-hashed and verify user password when needed.

There is also the need for the server to create a "NONCE" for the
first request, and is to be used thereafter. This "NONCE" will be used
between client and server to "authenticate the session"...i.e sent on
every request/response. This "NONCE" should time out after some time.
The server would generate a new "NONCE" after time-out. This "NONCE"
values is the "session" token. Of course in RESTful applications, the
server is stateless and clients manage and communicate, to the server,
their own state.

As for the multi-tenancy part, you may be wondering how the
application is going to scale. The restful design approach should
allow it to scale (more specialized machines see:
http://www.eecs.harvard.edu/~mdw/proj/seda/) fairly easily in a
distributed and clean fashion, when necessary. But for now it is not a
concern. I trust the restful architecture to be flexible enough to
allow for multi-machine scaling when the need arises.


Regard
Richard

On Feb 15, 7:59 am, Richard Mutezintare <transmet...@gmail.com> wrote:
> Yes the application needs to accommodate multiple tenants.
>
> Richard
>
> sent from android 2.2
> On Feb 15, 2011 2:04 AM, "Cristian Olaru" <col...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Hi Richard.
>
> > This is unclear for me. You want the application to be multitenant? See
> >http://en.wikipedia.org/wiki/Multitenancy
> > I think this can be done simple using AOP in background. I see something

> > like this in:http://www.grails.org/plugin/multi-tenant(Spring used in

> > background)
>
> > Otherwise I don't understand the use of this dis discriminator.
>
> > Regards...
>

> > On Tue, Feb 15, 2011 at 3:59 AM, transmeta01 <transmet...@gmail.com>

[transmeta01]

Has you completed the "company_id in every request" feature?

On Feb 15, 10:42 pm, transmeta01 <transmet...@gmail.com> wrote:
> HI Cristian,
>
> I pulled your commit and quickly ran through it. Very excellent work!
> The jetty plugin is a very good idea.
>
> The resource code is still very embryonic. For instance, no location
> (after creation of the new resource "user") is set for the creation of
> new user (newly registered user). I will fix that. The design is still
> in progress.
>
> Security considerations:

> Also onhttp://scrumy.com/classic, I posted a task that requires the

> > > like this in:http://www.grails.org/plugin/multi-tenant(Springused in