[jcifs] Preserve lastModified TIME

[Michael B. Allen]

On Wed, 28 Aug 2002 00:46:11 -0700
Conrad Minshall <conrad at apple.com> wrote:

> At 12:01 AM -0700 8/14/02, Michael B. Allen wrote:
> 
> >Chris,
> >
> >Here's an undocumented factoid for your docs: If LastModified is 0xFFFFFFFF
> >the  server  uses  "now". The docs say 0. I don't know if that works but it
> >probably doesn't or no windows clients do that or I would have used it.
> 
> The MacOSX smb client filesystem uses zero, which appears to work fine with
> Microsoft servers.  I expect to change to 0xFFFFFFFF as mimicing observed
> Windows packets is prudent.
> 
> Is there really supposed to be a server behaviour difference between 0 and
> 0xFFFFFFFF?  What is the observation (or spec even *grin*) in support of
> difference?

This is one of those situations where you should just do what NT4 does. NT4
is  the client with the most exposure so if you do what it does, you'll get
the same coverage and your safe. Anyone who writes a server will definately
test  rigorously  with  NT4.  The  only  reason  to deviate is when NT does
something insanely dumb (witness copy). 

jCIFS  mimics  NT4  almost  perfectly.  No other client that I know of does
this.  smbclient  doesn't  batch. Most clients do not support Unicode. With
some  minor  tweeking  (err  lying)  I  don't  think  anyone could tell the
difference  unless MS is hiding secret messages in alignment padding :-) As
a  result  I  feel  pretty  safe  that jCIFS  will work with just about any
server  out  there  (although  it's a little less forgiving about malformed
packets  and  junk left on the stream but I'm not sure if that's a bug or a
feature).

NT4 is "The Spec". 

-- 
A  program should be written to model the concepts of the task it
performs rather than the physical world or a process because this
maximizes  the  potential  for it to be applied to tasks that are
conceptually  similar and more importantly to tasks that have not
yet been conceived.