At 9:14 PM -0400 10/3/07, Mark Phippard wrote:
>This is all interesting. Perhaps we need to reopen this discussion
>(beyond just resource forks). Here's the deal though. We are closing
>in on the 1.5 branch date so people are really trying to focus on
>getting the final loose ends wrapped up so we can get the done.
No problem -- I certainly understand the situation.
I think I've proven to myself that some update to svn is needed to
accomplish what I need to convert over, and have a release to get out
myself, so I'm probably going to try and limp through on CVS for one
more release while we get this sorted out and will be glad to
participate as needed in the future.
(A friend has reminded me off-list of NTFS and UDF also having
multi-fork features and rsync's xattr support as a related example
which should be considered in a general solution)
>I'd suggest you start this thread over again after the release is done
>when people are in a frame of mind where we are defining the next
>If you think that patch you mentioned is the right approach, perhaps
>some people can work together to get it updated for current /trunk,
>cleaned up, some documentation, tests will be important etc.
I'll check w/Matt and some others -- even if it's not "the" right
approach, it feels like it's part of the right approach or at least a
good interim approach, in that files encoded this way do retain all
their data and could easily be converted to another encoding later.
The only issue I see is the one Brian Fitzpatrick brought up about
storing more than 64k in a property being a performance issue.
If the penalty isn't severe, and assuming we can just re-encode such
files in the future, once support for AppleSingle (or equivalent more
general solution) is available, this may be good enough to remove or
significantly reduce the entry barrier for Mac users and developers.
>Anyway, just wanted to let you know that for the sake of getting the
>release done a lot of us need to drop out of this discussion for a
>while and I did not want you to think you are being blown off.
No problem -- I'll let you guys get back to work for now and take a
look at Matt's patch as an interim solution.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Oct 4 16:07:07 2007