Hello, If you have tried to do any MIME processing using Haskell, you are likely to have found two things: 1) There are a lot of MIME libraries for Haskell 2) None of them do everything you want So, I propose that we form a MIME Strike Force and create the one, true MIME library. The plan is something like this: 1) Document all the things the MIME library needs to support. 2) Pick the technology, and design the infrastructure for supporting these features. For example, I don't think we will be able to use Parsec because: i) We want to support ByteString ii) We want to be able to lazily parse the message 3) Try to reuse as much existing code as possible to implement the design. I have started step 1 by creating this page: http://www.haskell.org/haskellwiki/Libraries_and_tools/MIMEStrikeForce Please add your comments, requirements, etc. If you are interesting in helping contrib ideas, code, or flames, please let me know. If there is enough interest, we should probably set up a mailing list for discussion. j. ps. This *might* make a decent SoC project, but only if it results in the one, true MIME library. We definitely do not need another incomplete MIME library floating around.
man, Micheal's minutes have been spamming my yahoo account
since like 2002. Think you could take care of that for me?
also, I'll write your mime library... my rate is $50 an hour
Dan
On 3/18/07, Jeremy Shaw
Hello,
If you have tried to do any MIME processing using Haskell, you are likely to have found two things:
1) There are a lot of MIME libraries for Haskell 2) None of them do everything you want
So, I propose that we form a MIME Strike Force and create the one, true MIME library.
The plan is something like this:
1) Document all the things the MIME library needs to support.
2) Pick the technology, and design the infrastructure for supporting these features. For example, I don't think we will be able to use Parsec because:
i) We want to support ByteString ii) We want to be able to lazily parse the message
3) Try to reuse as much existing code as possible to implement the design.
I have started step 1 by creating this page:
http://www.haskell.org/haskellwiki/Libraries_and_tools/MIMEStrikeForce
Please add your comments, requirements, etc.
If you are interesting in helping contrib ideas, code, or flames, please let me know. If there is enough interest, we should probably set up a mailing list for discussion.
j.
ps. This *might* make a decent SoC project, but only if it results in the one, true MIME library. We definitely do not need another incomplete MIME library floating around. _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
Jeremy Shaw wrote:
Hello,
If you have tried to do any MIME processing using Haskell, you are likely to have found two things:
1) There are a lot of MIME libraries for Haskell 2) None of them do everything you want
So, I propose that we form a MIME Strike Force and create the one, true MIME library.
The plan is something like this:
1) Document all the things the MIME library needs to support.
2) Pick the technology, and design the infrastructure for supporting these features. For example, I don't think we will be able to use Parsec because:
i) We want to support ByteString ii) We want to be able to lazily parse the message
3) Try to reuse as much existing code as possible to implement the design.
I have started step 1 by creating this page:
http://www.haskell.org/haskellwiki/Libraries_and_tools/MIMEStrikeForce
Please add your comments, requirements, etc.
If you are interesting in helping contrib ideas, code, or flames, please let me know. If there is enough interest, we should probably set up a mailing list for discussion.
j.
ps. This *might* make a decent SoC project, but only if it results in the one, true MIME library. We definitely do not need another incomplete MIME library floating around.
Good idea! I added a subsection for existing code to the wiki page, and added the multipart parser from the cgi package, which uses ByteStrings. /Björn
On Mar 18, 2007, at 21:36 , Jeremy Shaw wrote:
Hello,
If you have tried to do any MIME processing using Haskell, you are likely to have found two things:
1) There are a lot of MIME libraries for Haskell 2) None of them do everything you want
So, I propose that we form a MIME Strike Force and create the one, true MIME library.
The plan is something like this:
1) Document all the things the MIME library needs to support.
2) Pick the technology, and design the infrastructure for supporting these features. For example, I don't think we will be able to use Parsec because:
i) We want to support ByteString ii) We want to be able to lazily parse the message
3) Try to reuse as much existing code as possible to implement the design.
I have started step 1 by creating this page:
http://www.haskell.org/haskellwiki/Libraries_and_tools/MIMEStrikeForce
Please add your comments, requirements, etc.
If you are interesting in helping contrib ideas, code, or flames, please let me know. If there is enough interest, we should probably set up a mailing list for discussion.
j.
ps. This *might* make a decent SoC project, but only if it results in the one, true MIME library. We definitely do not need another incomplete MIME library floating around.
I added this as a SoC project proposal. We can decide on its merits when voting for the projects. See http://hackage.haskell.org/trac/ summer-of-code/ticket/1126 /Björn
participants (4)
-
Bjorn Bringert -
Björn Bringert
-
Dan Mead -
Jeremy Shaw