http://svn.apache.org/repos/asf/james/mime4j/trunk/src/main/java/org/apache/james/mime4j/Cursor.java contains a first cut at a cursor API
comments and improvements welcomed :-) a few particular points: 1. exception handling strategy - opted to through IOExceptions almost everywhere. when required, custom subclasses will be created. 2. there are currently some methods which seem like they may be stateful. for example, it's not certain how to interpret advanceToBoundary if boundary has not previously been set. the question is whether to specify reasonable behaviour (for example, when the boundary has not been set, advancedToBoundary should do nothing) or insist that exceptions be thrown. 3. the API uses a string to represent the MIME boundary. i'm not sure that this is right. AIUI (hopefully people will correct me if i'm wrong) this can only be 8 bit ASCII characters. in general, passing a string should mean worrying about encoding. realistically, the string will just be stripped to it's low order bytes. - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
