Sönke Ludwig
Sönke Ludwig
It wouldn't. It's just a representation of what is transferred in the request/response. The actual local cookie storage would be handled by a different entity (I guess this is what...
No, it contains all cookies that are set using `Set-Cookie`, or it contains all cookies that were sent in a `Cookie` header, depending on the direction.
You probably didn't refer to the type of `HTTPResponse.cookies` (`Cookie[string]`), right? That's what I thought.
`DictionaryList` conceptually maps from string to `T[]`, where `T` would be `Cookie` in this case.
Yes, I'd say it should be a `class` and be a member of `HTTPClient`, so that it can set the appropriate `Cookie` headers automatically. And there should be a global...
Excuse the unwanted pun in "jar"gon ;)
For cookies, there shouldn't be a serialization problem, because they are represented as `string` data anyway, so that serialization can be layered on top, if desired. But yeah, there still...
> > But yeah, there still needs to be a proper solution for the SessionStore (I need some time until I can really get to that). > > I'd vote...
I think we have some kind of misunderstanding there. Cookies are _always_ strings on the wire, so the core API can safely use that as the common denominator. Any serialization...
Basically, yes, the cookie's value would be a string. Something like the proposed database mirroring could happen in a system layered on top. It would call the database and it...