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
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
v-boun...@swift.org
> <mailto:swift-corelibs-dev-boun...@swift.org>
> Date: 11/17/2016 03:45AM
> Cc: swift-corelibs-dev <swift-corelibs-dev@swift.org
> <mailto:swift-corelibs-dev@swift.org>>
> Subject: 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
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
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=Code=✓) and am not opposed
to
>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.
> 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
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.
<mailto:willstant...@yahoo.com>>
>> Date: 11/08/2016 08:45AM
>> Cc: swift-corelibs-dev <swift-corelibs-dev@swift.org
>> <mailto:swift-corelibs-dev@swift.org>>
>> Subject: 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
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,
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
>
Hi there, I have spent some time working on a basic implementation of HTTPCookieStorage. In the process, I came across two crucial questions related to cookie persistence:1. How do you persist the cookies?2. Where do you persist them?In my current implementation
14 matches
Mail list logo