Return-Path: X-Original-To: apmail-commons-user-archive@www.apache.org Delivered-To: apmail-commons-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8664C11B6E for ; Sat, 17 May 2014 20:48:21 +0000 (UTC) Received: (qmail 88482 invoked by uid 500); 17 May 2014 20:40:13 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 87687 invoked by uid 500); 17 May 2014 20:40:13 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 85751 invoked by uid 99); 17 May 2014 20:20:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 17 May 2014 20:20:40 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.216.179] (HELO mail-qc0-f179.google.com) (209.85.216.179) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 17 May 2014 20:20:33 +0000 Received: by mail-qc0-f179.google.com with SMTP id x3so6546259qcv.24 for ; Sat, 17 May 2014 13:20:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=gfrW4CBPAWudA0fxF/iQuPMb+9CkbDWgSUh3zjVs6hY=; b=iBuLNBPKiylWtP4O7WZGSvaZ6zLfYM5dHW+bHyfmvX4Dge0LV7mLT3MP+OV7KxfikK nhPS5w4y6IhhrjMmVEdflvZfnaNjsQMSp4OUFzqXDU7VVJi3UuIxVwO6v8h7OA6Bsd9x 5sAIJzO01ggNx4NsnO48CCgfmyldxosiv8SGR1AjgXh35q0s/gj4CpVyD9L3hK+UsrNM JYwkz2+ZYzh286yYfX0Ia5gdAjakAffBa0KKUbo4kJvhD1SZlUHItMGefKHZFWJcT4BH j/Pvx5lJ2/iPXSpyRNRHVYFJYiAum6jeKO45m5p2uNFMmfej6AMv2+iygWaGhdgznc4H kt4A== X-Gm-Message-State: ALoCoQkzRnMjhCpWZEE4GZPBb3u58ILXD9WSTJi6ihrfQdJS6OsBHqopuYAndZimmZw0E2SixMzx X-Received: by 10.140.37.135 with SMTP id r7mr35183667qgr.61.1400358012056; Sat, 17 May 2014 13:20:12 -0700 (PDT) Received: from localhost (HSI-KBW-37-209-111-144.hsi15.kabel-badenwuerttemberg.de. [37.209.111.144]) by mx.google.com with ESMTPSA id h78sm7621047qgd.10.2014.05.17.13.20.11 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 17 May 2014 13:20:11 -0700 (PDT) Date: Sat, 17 May 2014 22:20:07 +0200 From: Bernd Eckenfels To: Commons Users List Cc: Schalk =?ISO-8859-1?Q?Cronj=05=05=E9?= Subject: Re: [VFS] LAST_MODIFIED vs GET_LAST_MODIFIED Message-ID: <20140517222007.000028d4.ecki@zusammenkunft.net> In-Reply-To: <53777462.7060009@gmail.com> References: <87kaqey4n5ct06a1jt76jkp1.1400336394045@email.android.com> <53777462.7060009@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hello, I have created https://issues.apache.org/jira/browse/VFS-527 for it. I think this is a two phase process as I would prefer not to break API compatibility and stay with the 2.1 version. It would be allowed to deprecate the LAST_MODIFIED and maybe a bite more cleanly describe the behaviour of GET/SET_LAST_MODIFIED_xxx (like: GET_LAST_MODIFIED allows to get the last modified date of files, it might also work on directories). or something? Gruss Bernd Am Sat, 17 May 2014 15:38:26 +0100 schrieb Schalk Cronj=05=05=E9 : > Suggestion [1] >=20 > Marking LAST_MODIFIED as deprecated, updating the docs to state that=20 > GET_LAST_MODIFIED means that the last modification time for a file or=20 > can be retrieved. >=20 > Suggestion [2] >=20 > Mark both GET_LAST_MODIFED and LAST_MODIFIED as deprecated. >=20 > Split GET_LAST_MODIFIED into a GET_LAST_MODIFIED_FILE and=20 > GET_LAST_MODIFIED_FOLDER. I am saying this as by example on S3 it is=20 > possible to get the last modification time of a blob, but not on=20 > something marked as a directory marker. >=20 > Disclaimer: Maybe it is possible to get modification time on > directory marker on S3, but i have based it upon what jClouds can do. >=20 > On 17/05/2014 15:19, Gary Gregory wrote: > > I suppose... not sure what the best path is. You pick ;) > > > > Gary > > > > > > -------- Original message -------- > > From: Bernd Eckenfels > > Date:05/16/2014 21:42 (GMT-05:00) > > To: Schalk Cronj=05=05=E9 > > Cc: user@commons.apache.org > > Subject: Re: [VFS] LAST_MODIFIED vs GET_LAST_MODIFIED > > > > Hallo, > > > > Really no idea, it is not used anywhere. And GET_LAST_MODIFIED is > > there since the 1.0 API, so it can not even be explained with > > backward compatibility. There is also nothing in JIRA or the Wiki. > > > > I guess I would put a deprecated tag in javadoc and forget about it? > > > > Gruss > > Bernd > > > > > > Am Wed, 14 May 2014 22:52:19 +0100 schrieb Schalk > > Cronj=05=05=E9 : > > > > > One more Capability question. Javadoc states that > > > > > > GET_LAST_MODIFIED: File get last-modified time is supported. > > > LAST_MODIFIED: File last-modified time is supported. > > > > > > These seems to be the same thing. Furthermore there is no > > > reference to LAST_MODIFIED in the core code base, only to > > > GET_LAST_MODIFIED (and also to SET_LAST_MODIFIED_xxx). Is > > > LAST_MODIFIED a deprecated capability? > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: user-unsubscribe@commons.apache.org > > For additional commands, e-mail: user-help@commons.apache.org > > >=20 >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@commons.apache.org For additional commands, e-mail: user-help@commons.apache.org