-Original Message-
From: Antonio Chirizzi [mailto:[EMAIL PROTECTED]
Sent: 25 June 2005 18:32
To: James Developers List
Subject: Re: IMAP for James: offering help to development
Jason,
I checked out all the sources from the link.
I can see two directories named imap and imap2,
I managed to make MX4J reply with xml via the HTTP by programmatically
changing the XSLT Processor to a default processor, but to do this we
have to insert a new class in Phoenix to replace the MX4JSystemManager
since all this config is hard coded into that class.
We could do that, or, we can
It's my understanding that if we go the XML-RPC route, we have to add
a second webserver to the console, dedicated solely to handling the
XML-RPC requests. Do we want to do that?
I definitely agree on the bare-bones JSP/Servlets framework for the
console, though.
On 6/27/05, Juan Carlos
I read a lot of myisam or innodb databases.. but it is difficult to choose
one of them...
myisam, is much faster than innodb, but innodb has more security (transaccions
and row-level rocking).
is it possible to use james with myisam and dont less the security, i mean,
perhaps.. it is a way en
You are right, considering that there is an http server in MX4J. But we
would not need to have both running, we could live off the XML-RPC one
without using the other one, which is turned off by default anyway.
On Mon, 2005-06-27 at 12:27 -0500, Anne S wrote:
It's my understanding that if we
What are you thinking of using to serve the servlets?
Steve
-Original Message-
From: Juan Carlos Murillo [mailto:[EMAIL PROTECTED]
Sent: Monday, June 27, 2005 2:18 PM
To: Anne S
Cc: James Developers List
Subject: Re: Proposal for Web Admin Console
You are right, considering
From previous suggestions and discussions the best fit would seem to be
Jetty. But Noel mentioned that we might not want to include the app
server in James itself, so if it is not embedded it won't matter what
serves them as long as we stay inside J2EE, we would just provide the
WAR and let the
http://dev.mysql.com/doc/mysql/en/corrupted-myisam-tables.html
According to this link, killing mysqld or turning off the computer in
mid-write could result in table corruption with MyISAM. Not too
surprising considering it doesn't support transactions. I personally
would find this
In the case of hardware failure, no database on this planet can 'guarantee'
there will be no corruption, if you have a single point of failure, and it
fails, everything fails, hence the term single as opposed to many points of
failure.
One of the most important things about software design, in
Hi Simon,
Simon Funnell wrote:
In the case of hardware failure, no database on this planet can 'guarantee'
there will be no corruption, if you have a single point of failure, and it
fails, everything fails, hence the term single as opposed to many points of
failure.
Of course, it's not
Hi Joe,
http://dev.mysql.com/doc/mysql/en/ansi-diff-transactions.html
This is good read, my point is that the choice to use either MyISAM or
INNODB tables depends on how the james application code (of which I am not
aware in this case) is implemented.
If anyone asks you if you glass is half
[1] If you're not familiar with the mechanics of journaling, see Chapter
7 of:
http://www.nobius.org/~dbg/practical-file-system-design.pdf
Filesystem heaven.
http://www.namesys.com/
Simon
- Original Message -
From: Joe Cheng [EMAIL PROTECTED]
To: James Developers List
12 matches
Mail list logo
