I've gone ahead and implemented the patch as discussed, which does the following:
- Implements the padding for sequential file names, padding ten zeroes to the name (enough to handle as many digits as can be generated by a 32-bit int). This allows the names to be sorted by natural order.
- Removed the server sorting the list of children, leaving it up to the client to do so if it wishes. This could give a very slight performance bump, particularly when dealing with directories with a large number of files.
- Updated the Javadoc to reflect this change in both versions of the getChildren method.
- Adds a unit test that checks that the sequential file names are being created correctly.
I thought about adding a GetChildrenSorted or such method, but since it's really easy for the client to sort the list once returned (java.Collections.List.Sort(children)), it seems like it would be more work to add and support these methods.
Hope this is useful.