[jcifs] Last Access Time and Owner of a File using JCIFS

[Michael B Allen]

On Dec 21, 2012 1:40 PM, "Matt Munz" <Matt_Munz at symantec.com> wrote:
>
> Mike,
>
> > The code is not very active right now ...
>
>   Which code are you talking about? Are you saying that jCIFS as a whole
is not being actively developed? If so, how about maintenance -- is it
being actively maintained, or are bugs (e.g. security bugs) not being
resolved in a timely manner?
>
> > ... I don't think they're even on the TODO list to be honest.
>
>   Sure.  I wouldn't presume to set your priorities. I guess I'm asking
what would be necessary to get these things in -- what are the things that
need to happen to get this functionality into jCIFS? For a person who
requires this functionality, obviously they could maintain a fork that
includes it, but I think we can all agree (for that person and probably the
community as well) that it is preferable to merge that fork back in with
the jCIFS codebase.
>
>   I'm not volunteering to do that work, but I am just wondering what
would be involved so that I can evaluate the options. Presumably this work
is non-trivial or else you would have merged in this code already, but I'm
hoping it's not an overwhelming amount of work either.
>
> > The patches directory is not for patches that are to be merged.
>
>   Yeah, I understand that.  This is like your "contrib" folder or
whatever.  Again, I'm just asking what it takes to move this
code/functionality from "contrib" (or whatever) to "main".  Maybe the code
has to be re-written, pass some test suite, etc.  I'm just trying to figure
out what that process / set of requirements is.

Hi Matt,

The code (jcifs) is 14 years old so months can go by between releases. And
what is released is usually only critical or trivial. Adding LastAccessTime
or similar would require an API change which is generally considered to be
a more significant change (it introduces something that can break).
Realistically, we cannot satisfy everyone's needs. Some people are just
going to have to maintain their own fork.

The API changes you're requesting should be applied but the project is in a
dormant mode right now.

Mike

>
>   Cheers,
>
> Matt Munz
> Principal Software Engineer, Symantec Corporation
> www.symantec.com
> matt_munz at symantec.com
>
> This message (including any attachments) is intended only for the use of
the individual or entity to which it is addressed and may contain
information that is non-public, proprietary, privileged, confidential, and
exempt from disclosure under applicable law or may constitute as attorney
work product. If you are not the intended recipient, you are hereby
notified that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and (i) destroy
this message if a facsimile or (ii) delete this message immediately if this
is an electronic communication.
>
> -----Original Message-----
> From: Michael B Allen [mailto:ioplex at gmail.com]
> Sent: Thursday, December 20, 2012 10:15 PM
> To: Matt Munz
> Cc: jcifs at lists.samba.org
> Subject: Re: [jcifs] Last Access Time and Owner of a File using JCIFS
>
> On Wed, Dec 19, 2012 at 2:18 PM, Matt Munz <Matt_Munz at symantec.com> wrote:
> > Hi Mike,
> >
> >   I'm new to the list and I'm unfamiliar with the JCIFS
development/release process so my apologies if I'm treading old ground here.
> >
> >> There are no plans to add these features to JCIFS in the near future.
> >
> >   What about the not-so-near future? Can you make a rough guess when
these will be released? Presumably those patches will be merged in to the
main branch at some point.  What's necessary to get that to happen?
>
> Hi Matt,
>
> The code is not very active right now and the features you describe
> are super high priority. In fact I don't think they're even on the
> TODO list to be honest.
>
> The patches directory is not for patches that are to be merged. On the
> contrary its for stuff that wasn't really interesting enough to be
> incorporated. But if the patch is something that I thought someone
> might be remotely interested in, I just drop it in the patches
> directory.
>
> Mike
>
> > -----Original Message-----
> > From: jcifs-bounces at lists.samba.org [mailto:
jcifs-bounces at lists.samba.org] On Behalf Of Michael B Allen
> > Sent: Saturday, December 15, 2012 2:28 PM
> > To: Aravindan
> > Cc: jcifs at lists.samba.org
> > Subject: Re: [jcifs] Last Access Time and Owner of a File using JCIFS
> >
> > On Tue, Dec 11, 2012 at 12:18 PM, Aravindan <aravindan.t at gmail.com>
wrote:
> >> Hello,
> >>   In the current implementation of jCIFS 1.3.17, there is no
capability for
> >>
> >> 1. Getting the Last Access Time of a file
> >> 2. Setting the Last Access Time of a file
> >> 3. Getting the Owner of a file
> >>
> >> Just wanted to know if jCIFS community has plans to add the above
mentioned
> >> capabilities anytime in the near future.
> >
> > Hi Aravindan,
> >
> > That information is actually received when reading security
> > descriptors. It is just not decoded or exposed through the API. But
> > there are fairly simple patches in the patches/ directory that
> > illustrate how add this sort of functionality. I think there's even a
> > patch for setting the Last Access Time.
> >
> > There are no plans to add these features to JCIFS in the near future.
> >
> > Mike
> >
> > --
> > Michael B Allen
> > Java Active Directory Integration
> > http://www.ioplex.com/
>
>
>
> --
> Michael B Allen
> Java Active Directory Integration
> http://www.ioplex.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/jcifs/attachments/20130124/76cff283/attachment.html>