drop cookies.dat, not required, not thread safe

[FernetMenta]

fix http://trac.kodi.tv/ticket/16935

A systemwide storage for cookies makes no sense and is not thread safe. We may have multiple CURL sessions open at once.

[mention-bot]

@FernetMenta, thanks for your PR! By analyzing the history of the files in this pull request, we identified @notspiff, @mkortstiege and @Rawk to be potential reviewers.

[kib]

I don't see the benefit in this either. The cookies.dat shared storage doesn't select the correct cookie anyway. Dropping it makes more sense - the cookie should only exist in the session content.

[arnova]

This may also fix http://trac.kodi.tv/ticket/16849

[arnova]

Btw. expect breakage for some stuff, this was once implemented for a reason (not by me) I guess.

[FernetMenta]

Since having a global cookie store is wrong by design, I don't expect any well designed behaviour to break.

this was once implemented for a reason

maybe, maybe not. the code was very old. maybe the author was not aware that cookie engine could be enabled without having a file, or this is some later feature of libcurl.

[fritsch]

+1

[arnova]

@FernetMenta : Please note that I'm fine with this change nevertheless since this obviously can never work for multithread.