Hi,
At 08:18 2/11/00 -0500, you wrote:
>Hello,
>I've jsut come across JAMES and am thinking of using it in
>a project.
kewl ;)
>I'm trying to create a server for hosting online discussion which
>supports many protocols (web based, mailing lists, NNTP ...)
very kewl - something I have wanted to do aswell ;) Actually something I
was going to attempt to do with james ;)
>but it also needs to store its messages as XML.
>
>I suppose I have two questions.
>How much work would be required to make JAMES store messages
>as XML files?
it would be very easy (just a matter of adding one class and changing
config file)
>Can james be setup for multi user use? ie. mailing lists, NNTP rather than
>individuals mail boxes.
It *can" be but it is not yet optimal for that due to locking that can
occur. I haven't looked at new database repository but I believe that may
solve some of the problems.
>I've just graduated (Computer Science) and enjoyed my 3rd year
>project so much that i want to continue it. My project essentially solved
>two problems:
>- The archive created once a discussion forum (mailing list,...)
>has existed for a while becomes a mass of messages,
>which are largely quotes and difficult to navigate
>through.
;)
>- Discussion forums are often fragmented by protocol which seems
>an odd way to separate people with common interests.
>
>I implimented a discussion server in java. Think of it like a
>news server. However, it was protocol independent. I wrote a
>different class for each protocol but all classes used the same
>class to store there messages. I only actually implimented NNTP
>and HTTP. So there was a server you could connect to and browse
>with your news reader or web browser. This solved the second
>problem.
sounds very kewl. Is the project opensource ?
>The next step in terms of functionallity is adding more protcols (IMAP, POP)
>and better parsing to improve the quote finding success.
right. SMTP and POP (and eventually IMAP) are in James atm.
>However, my project was unreliable and didn't scale. I've realised I should
>have built on existing systems. This is what
>I'm trying to do now. I want to know if I can use james as the
>presentation layer. I can then get on with parsing messages
>trying to find good ways to mark up the messages.
The way I see it there is 3 layers.
* The backend that stores and manages messages
* The middlelayer that acts as distribution points (ie http, nntp, smnt,
jabber)
* presentation layer that makes it look good (ie web stuff is styled etc)
>I'm also interesed in using cocoon to convert the messages
>from XML to rfc822 and other formats. using cocoon would speed
>up browsing the archive over the web because of its caching.
>This was one of the big problems I encountered
Interesting - could you expand on this ?
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]
