Hi,

> -----Original Message-----
> From: Noel J. Bergman [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 10, 2003 10:29 AM
> To: James Users List
> 
> > Could you give some advice on how to handle file-based virtual users?
> 
> Robert Cadena wrote one (http://www.machine501.com/projects/).  I had
> hoped
> that he'd submit a patch that merged his mailet and JDBCVirtualUserTable
> under a common based class.  I will probably look into that shortly.  If
> there were such a common class, all that you'd have to do would be to
> provide support for your XML format.

Perfect! Makes me wonder how many other cool projects are out there. I can't
seem to find them through google (the word 'james' is tough to search and
get relevant hits).

> 
> > How many users would you consider too much for a file-based setup?
> 
> If you cache the virtual user table in memory, you could arguably handle
> 1000s of users in a small amount of memory relative to the cost of the
> database, and with excellent performance.  More of an issue would be
> dynamic
> reconfiguration.

That works for me.

> 
> > is there a way to transform XML marked-up email to a standardized email
> format?
> 
> The nice way to do that would be to include a Cocoon pipeline into James.
> I'd love to see that happen.

Do you want a cocoon pipeline for an example integration? I just asked on
cocoon-dev if anything exists and received one response from a committer, so
far, saying they haven't heard of anything. Do you have any basic
instructions on how this could be integrated? Is it a mailet? Processor?
Something else? In other words, how do you dump it off to the pipeline for
processing?

Would a generic pipeline/filter/mailet/processor be appropriate? (Don't know
if I would want to incur cocoon's overhead for this simple task).

Best,
-Rob

> 
>       --- Noel
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to