>Anyway, so it wasn't a very productive weekend for me. Once Charles gets
>the MailRepository code integrated, I'm going to write a database interface
>using this Town API we use everywhere in our company
>(www.working-dogs.com/town). I'm sure others will just want to use raw
>java.sql, but the Town API is nice because it'll handle connection pooling
>and we've found the API to manage records in a table easier.
Town is great :P - I haven't looked at it yet but I assume torque can be
used to generate wrappers for persistent objects to use town ? (Torque is
from Turbine in case you didn't know).
I am just curious are you sure that you don't want to extend James to
include lots of different Messagetypes and extend Mailet api to more be a
Messagelet api ? The reason I ask is that I am slowly putting away a new
server and many of the things I am tackling are similar to James - ie I
have written my own SMTP server that could benefit James. I have already
generated and thrown away at least 10 different DB designs for message
store :P which is where you are going to go next I guess.
Even if we can't collaborate perhaps if we discuss issues it could help us
both. Some of my stuff will eventually make it's way into Avalon CVS which
we can collaborate on.
My main concern is that I have to have a generic messaging server - ie
NNTP/IMAP/POP3/SMTP/Other message feeds like news feeds via OCS etc. If I
can I also want to integrate it with an IM solution.
Anyways thoughts ?
Cheers,
Pete
*------------------------------------------------------*
| "Nearly all men can stand adversity, but if you want |
| to test a man's character, give him power." |
| -Abraham Lincoln |
*------------------------------------------------------*
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
