[jcifs] Changes in jCIFS
Michael B Allen
ioplex at gmail.com
Tue Aug 2 19:29:25 MDT 2011
On Tue, Aug 2, 2011 at 2:51 PM, Christopher R. Hertel <crh at samba.org> wrote:
> Michael B Allen wrote:
>>> Moreover, the regular behavior for OpenSolaris and FreeBSD is, that the
>>> files get sorted alphabetically descending, so the last file is at the
>>> bottom. Are there some cases in which the last file is at the top?
>> Again, there is no spec so there is nothing that says that the "last
>> file index" has to be at the end of the message. But I don't recall
>> ever seeing an message that did not place the last file at the end of
>> the message.
> There should be a specification for this. Which call is it? Let me know
> and I will look it up. If it's not specified, I can file a documentation
> bug report.
I am aware of the work that you have done on the Microsoft Windows
protocol documents in this area. But as I pointed out earlier in the
thread, no such documentation existed when all of the servers like
Samba, iSeries, EMC, etc (or Windows) were written. So everyone just
wrote and tested their code until the various Windows clients were
satisfied. And that is largely why we see variation in what the
lastNameOffset field of the TRANS2_FIND_FIRST2 response actually
points to and I believe it is why we have seen issues with listing
files on iSeries and the server Marco is using (Solaris was it?).
Notice the following comment in Trans2FindFirst2Response.java:
/* lastNameOffset ends up pointing to either to
* the exact location of the filename(e.g. Win98)
* or to the start of the entry containing the
* filename(e.g. NT). Ahhrg! In either case the
* lastNameOffset falls between the start of the
* entry and the next entry.
Of course we don't care about Windows 98 or NT anymore.
Michael B Allen
Java Active Directory Integration
More information about the jCIFS