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=Code=✓) and am not opposed to

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.

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

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

Furthermore isn’t it a bit of a conflict if we have multiple versions of Foundation running apps on a server? I would expect that the mutable state of cookies should never be shared across processes not just from a security standpoint but also from a versioning standpoint. Let have a scenario

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