james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman" <n...@devtech.com>
Subject RE: Stroage Quota - need advice
Date Mon, 03 Jun 2002 06:15:32 GMT
How does this differ from any other property of a JamesUser?  Is there a
reason why quota isn't a simple property added to JamesUser and implemented
by DefaultJamesUser?  Why is configuring and managing that value any
different from configuring and managing a property such as the forwarding

My thought, in response to your example, was that if JamesUser.getQuota() ==
0, then the matcher could use the parameter passed to it in the config file.
The parameter provides a global default.

Am I missing something here?  Not counting the admin program, do we need do
more than add the bean property to JamesUser, add a standard bean property
implementation to DefaultJamesUser, add a couple of lines to
JamesUsersJdbcRepository, update the SQL resources file, and add some code
to RemoteManagerHandler?

	--- Noel

-----Original Message-----
From: Serge Knystautas [mailto:sergek@lokitech.com]
Sent: Monday, June 03, 2002 1:38
To: James Developers List
Subject: Re: Stroage Quota - need advice

Good point.  I can see how different users would have different quotas.
  Ok, so if we change (I don't want to call it extend as that implies
some OO stuff) JamesUser to support quotas, how do you configure (e.g.,
a default) and manage that?
Serge Knystautas
Loki Technologies - Unstoppable Websites

Noel J. Bergman wrote:
>>I might tweak the matcher to look like this though...
>><mailet matcher="UserOverQuota=6m" class="ToProcessor">
> I disagree on the grounds that we extend JamesUser to include a quota
> property.  This means that the matcher would check each user's quota, and
> reject each one for which that message would create the over quota
> condition.
> That is why there was no parameter to the matcher, although there could be
> default for when the user's quota is not explicitly set.

To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>

To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>

View raw message