Norman Maurer wrote: > Niklas Therning schrieb: > >> Norman Maurer wrote: >> >> >>> Hi guys, >>> >>> after using mime4j a little bit to implement some actions which should >>> get taken for specific message parts I'm a little bit "unhappy" with it... >>> Its ok for using in a single Thread programm, but with using multiply >>> Threads its not really "good". For example i have to use one >>> MimeStreamParser per InputStream I want to parse.. Anyone allready >>> thought about rewrite some parts of mime4j to allow ThreadSafe usage of >>> MimeStreamParser and the ContentHandlers ? >>> >>> >>> >> Hi, >> >> Could you please describe in more detail what it is you are trying to >> achieve? As MimeStreamParser is a push kind of parser (like SAX) I >> cannot really see how one would use it concurrently from multiple threads. >> >> Or are you talking about the classes in org.mime4j.message (the DOM like >> stuff)? It would make more sense to me to use those classes from >> multiple threads. >> >> >> > Hi Niklas, > > sorry for this... I think you are right, I was a bit to fast :-/ >
No problem! :-) > BTW, What is the next think you want to see in MIMI4J ?I whould be > intressted in work on it but at the moment I have no Idea ... > Well, I'd like to sort out the performance issues. None of the code has been optimized for performance yet so it might be time now. Another cool thing would be to convert MimeStreamParser into a pull like parser (like StAX). That would make it a lot more flexible. We could still retain full backwards compatibility since it would be trivial to rebuild the push parser on top of the pull parser. There are also some common header fields which we don't have parsers for (like Received). Take your pick! ;-) -- Niklas Therning www.spamdrain.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
