You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Chris Means <cm...@intfar.com> on 2003/06/09 21:55:58 UTC
Mailet Idea...
Hey,
I've been thinking I need a new mailet, before I start to write it, I wanted
to make sure there weren't any obvious limitations, or simply a better way
to do it.
Essentially, I've found the need to have some sort of a scheduler (time not
message based), that could report either on internal James statistics, or
possibly a review of messages waiting etc..
Though it would be simple enough to write something that runs outside of
James for some of the statistics etc., I was thinking that a mailet (without
a matcher) would also support this same idea, if it's possible to have a
mailet without a matcher (or maybe a matcher that never matches anything
<g>). Having James load it as a matcher saves me the trouble of having to
configure and run a new process.
This Scheduler Mailet would have init parameters describing the classes and
scheduled runtimes (probably sets of hours etc.). Any class that supported
the Runnable interface could be called.
Are there any issues with new threads being spawned from within James by a
mailet?
Any comments on the above outline (as poorly as it's written...it's just
some serialized thoughts)?
Thanks.
-Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
Re: Mailet Idea...
Posted by Søren Hilmer <sh...@itplus.dk>.
We have done something like this, but instead of using a Mailet, we wrote it
as a Phoenix service instead.
I believe that this sort of task is better more suited at the Phoenix service
layer than in a Mailet.
-- Søren
On Monday 09 June 2003 21:55, Chris Means wrote:
> Hey,
>
> I've been thinking I need a new mailet, before I start to write it, I
> wanted to make sure there weren't any obvious limitations, or simply a
> better way to do it.
>
> Essentially, I've found the need to have some sort of a scheduler (time not
> message based), that could report either on internal James statistics, or
> possibly a review of messages waiting etc..
>
> Though it would be simple enough to write something that runs outside of
> James for some of the statistics etc., I was thinking that a mailet
> (without a matcher) would also support this same idea, if it's possible to
> have a mailet without a matcher (or maybe a matcher that never matches
> anything <g>). Having James load it as a matcher saves me the trouble of
> having to configure and run a new process.
>
> This Scheduler Mailet would have init parameters describing the classes and
> scheduled runtimes (probably sets of hours etc.). Any class that supported
> the Runnable interface could be called.
>
> Are there any issues with new threads being spawned from within James by a
> mailet?
>
> Any comments on the above outline (as poorly as it's written...it's just
> some serialized thoughts)?
>
> Thanks.
>
> -Chris
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: james-user-help@jakarta.apache.org
--
Søren Hilmer, M.Sc.
R&D manager Phone: +45 70 27 64 00
TietoEnator IT+ Fax: +45 70 27 64 40
Ved Lunden 12 Direct: +45 87 46 64 57
DK-8230 Åbyhøj Email: soren.hilmer@tietoenator.com
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
Re: Mailet Idea...
Posted by Marco Tedone <mt...@jemos.org>.
Chris, you may want to incorporate your idea in jamailet.
If interested, have a look at the following site:
http://sourceforge.net/projects/jamailet/
Regards,
Marco
----- Original Message -----
From: "Chris Means" <cm...@intfar.com>
To: "James Users List" <ja...@jakarta.apache.org>
Sent: Monday, June 09, 2003 8:55 PM
Subject: Mailet Idea...
> Hey,
>
> I've been thinking I need a new mailet, before I start to write it, I
wanted
> to make sure there weren't any obvious limitations, or simply a better way
> to do it.
>
> Essentially, I've found the need to have some sort of a scheduler (time
not
> message based), that could report either on internal James statistics, or
> possibly a review of messages waiting etc..
>
> Though it would be simple enough to write something that runs outside of
> James for some of the statistics etc., I was thinking that a mailet
(without
> a matcher) would also support this same idea, if it's possible to have a
> mailet without a matcher (or maybe a matcher that never matches anything
> <g>). Having James load it as a matcher saves me the trouble of having to
> configure and run a new process.
>
> This Scheduler Mailet would have init parameters describing the classes
and
> scheduled runtimes (probably sets of hours etc.). Any class that
supported
> the Runnable interface could be called.
>
> Are there any issues with new threads being spawned from within James by a
> mailet?
>
> Any comments on the above outline (as poorly as it's written...it's just
> some serialized thoughts)?
>
> Thanks.
>
> -Chris
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: james-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
RE: Server Statistics (was RE: Mailet Idea...)
Posted by "Noel J. Bergman" <no...@devtech.com>.
Søren Hilmer wrote:
> We have done something like this
Steve Short added:
> That said, I would rather see statistics exposed via JMX interfaces, and
> then use an external tool to pull statistics when required.
Feel free to help. :-)
Some discussion is archived at
http://archives.apache.org/eyebrowse/BrowseList?listName=james-dev@jakarta.a
pache.org&by=thread&from=225096
I don't know if Jason Webb did any further work on it.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org
Server Statistics (was RE: Mailet Idea...)
Posted by "Noel J. Bergman" <no...@devtech.com>.
> Essentially, I've found the need to have some sort of a scheduler (time
not
> message based), that could report either on internal James statistics, or
> possibly a review of messages waiting etc.
You don't want a mailet. You want a service. Look at FetchMail, for
example, which is a scheduled service. Really quite straightforward.
Besides, in James v3, you won't be able to access internals from a Mailet.
Before you go too far down this road, you should search the archives. There
was a lengthy discussion of server statistics last year, with some sample
code and other directions. It would be a very good thing to have, but you
will want to read some of the prior material. :-)
> This Scheduler Mailet would have init parameters describing the classes
and
> scheduled runtimes (probably sets of hours etc.). Any class that
supported
> the Runnable interface could be called.
You really want a Service, where you will have full access to an XML
descriptor.
> Are there any issues with new threads being spawned from
> within James by a mailet?
RemoteDelivery does it. :-)
> Any comments on the above outline (as poorly as it's written...it's just
> some serialized thoughts)?
Did I mention that you want to write a Service? ;-)
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: james-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-user-help@jakarta.apache.org