Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

Hello Created a PR https://github.com/apple/swift-corelibs-foundation/pull/889 for the XDG file specification implementation, extending from the work Tony Parker shared below. But still the question remains as to how we could test this without adding exposed API from the Foundation side. We could i

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

In my opinion, cookies should go into $XDG_DATA_HOMEBut, there was an opinion sometime back, that cookies could go into a `.config` directory. So, I am wondering if $XDG_CONFIG_HOME is also a candidate here :-)Pushkar N Kulkarni, IBM RuntimesSimplicity is prerequisite for reliability - Edsger W. Di

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

Hello @Tony:Thanks for sharing. I would like to build upon it from here.@allI need guidance on which XDG environment directory path the cookie storage would fit in?Would XDG_CONFIG_HOME be a best fit for the cookies?  Request your inputs to put me in the right direction. Thanks!-MamathaIBM Runtimes

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

> Sent by: anthony.par...@apple.com <mailto:anthony.par...@apple.com> > Date: 01/20/2017 11:28PM > Cc: Will Stanton mailto:willstant...@yahoo.com>>, > swift-corelibs-dev <mailto:swift-corelibs-dev@swift.org>> > Subject: Re: [swift-corelibs-dev] Implementing HTTPCook

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

Hi Tony, Thanks! A starting point will really help. I've filed a feature request on JIRA: https://bugs.swift.org/browse/SR-3697Pushkar N Kulkarni, IBM RuntimesSimplicity is prerequisite for reliability - Edsger W. Dijkstra -anthony.par...@apple.com wrote: -To: Pushkar N Kulkarni

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

libs-dev-boun...@swift.org > <mailto:-swift-corelibs-dev-boun...@swift.org> wrote: - > To: Will Stanton mailto:willstant...@yahoo.com>> > From: Tony Parker via swift-corelibs-dev > Sent by: swift-corelibs-dev-boun...@swift.org > <mailto:swift-corelibs-dev-boun...

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

Hi Tony, Will, others: Apologies for bringing this up after a long time!I hope we still agree on the use of the "XDG Base Directory Specification". I did a quick read of the spec document. I am happy to file a JIRA report for this.The scope, as I understand it is: CoreFoundation will implement the

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

Hi Will, > On Nov 14, 2016, at 12:56 PM, Will Stanton wrote: > > Hello Tony, > > Thanks for the reply. About XDG_DATA_HOME, the variable is undefined on my > desktop-less server, and I think many processes still have their own save > locations. > Still, I can believe its used in a lot of plac

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

Hello Tony, Thanks for the reply. About XDG_DATA_HOME, the variable is undefined on my desktop-less server, and I think many processes still have their own save locations. Still, I can believe its used in a lot of places (https://github.com/search?q=XDG_DATA_HOME&type=Code&utf8=✓) and am not op

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

>From my (potentially limited) experience, I would say that yes, many tools out >there do follow this spec. I only have anecdotal evidence to back this up, but I think many new tools use this convention, and those that don't do not out of long-standing conventions that say otherwise (e.g. `~/.vi

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

> On Nov 14, 2016, at 10:47 AM, Will Stanton wrote: > > Hello Tony and Philippe, > > I don’t think it would be odd for cookie/setting files to be in a folder > named after Foundation (namely ~/.foundation): > - The files are owned by Swift/Linux Foundation in the sense Foundation > writes the

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

Hello Tony and Philippe, I don’t think it would be odd for cookie/setting files to be in a folder named after Foundation (namely ~/.foundation): - The files are owned by Swift/Linux Foundation in the sense Foundation writes them, and Foundation is the only one that should access them directly.

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

;> >> -Will Stanton mailto:willstant...@yahoo.com>> >> wrote: - >> To: Pushkar N Kulkarni/India/IBM@IBMIN >> From: Will Stanton mailto:willstant...@yahoo.com>> >> Date: 11/08/2016 08:45AM >> Cc: swift-corelibs-dev > <mailto:swift-coreli

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

.@yahoo.com>> > wrote: - > To: Pushkar N Kulkarni/India/IBM@IBMIN > From: Will Stanton mailto:willstant...@yahoo.com>> > Date: 11/08/2016 08:45AM > Cc: swift-corelibs-dev <mailto:swift-corelibs-dev@swift.org>> > Subject: Re: [swift-corelibs-dev] Implementi

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

Thanks Will! "NSHomeDirectory() + "/.foundation/Cookies/shared" seems good to mePushkar N Kulkarni, IBM RuntimesSimplicity is prerequisite for reliability - Edsger W. Dijkstra -Will Stanton wrote: -To: Pushkar N Kulkarni/India/IBM@IBMINFrom: Will Stanton

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

Was wondering if there could be a common directory for Foundation-related files, such as NSUserDefaults in addition to cookie storage? So maybe for cookies: NSHomeDirectory() + "/.foundation/Cookies/shared" And settings for an app/service: NSHomeDirectory() + "/.foundation/Preferences/EXECUTABLE

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

I’m for locating it in the same place on all platforms. In general, I’m tired of digging around in different places for stuff depending on which flavor I’m using. -Kenny > On Nov 7, 2016, at 2:45 PM, Tony Parker via swift-corelibs-dev > wrote: > > Hi Pushkar, > > Good question. If this wer

Re: [swift-corelibs-dev] Implementing HTTPCookieStorage

Hi Pushkar, Good question. If this were Darwin I guess I would say ~/Library/Application Support — but I don’t know what the best practices are on other platforms. Does anyone out there have some suggestions? - Tony > On Nov 7, 2016, at 11:09 AM, Pushkar N Kulkarni via swift-corelibs-dev > w