Etienne Cimon

I think an array would be necessary because two cookie names can co-exist if it's for a different domain, or even within the same domain depending on if it's a...

It's also missing a multi-part form writer I think?

I was thinking of something more in line with this: ``` struct CookieJar { Array!Cookie cookies; bool insert(string setCookieStr); // Takes the value part from Set-Cookie: [...] bool insert(Cookie cookie);...

How would the CookieValueMap know which Cookies it needs to replace or expire?

So CookieValueMap is a single Cookie from the HTTPClientResponse's Set-Cookie commands ?

Isn't a DictionaryList a string string map? So it would map Cookie name and string values? How would this fit in the DictionaryList for example: Set-Cookie: PREF=ID=3d9141136c1c76fc:FF=0:TM=1399542170:LM=1399542170:S=kETqNOhXHlbP98Fl; expires=Sat, 07-May-2016 09:42:50...

Ok! I was assuming it would stay string string[] to map the fields of a cookie like the InetHeaders. So the CookieJar would be handled outside of HTTPRequest / HTTPResponse?

> BTW, "store" vs. "jar" - my preference would be "store", is "jar" some kind of standard jargon? Yes, it's very widespread, I saw it in every framework I came...

> Still not sure if I find the cookie jar class name funny or silly, but if everyone names it like that... heh :-p > But yeah, there still needs...

> Regarding serialization, the point is that the underlying storage format is always a string, so that this doesn't have to be templated. The SessionStore on the other hand has...