Hi Stanislav,
My reasoning for this is as follows.
1. The session_set_cookie_params function requires a lifetime parameter
at the moment.
2. To enforce that lifetime stays required I did not want to make it
required within the optional array. That would make that optional array
not optional anymore, and even have a required key. I don't think that
is a good idea.
3. To prevent that the array of options is different between the three
functions (session_set_cookie_params, setcookie, setrawcookie), I chose
to exclude lifetime from the array of options and include it in the list
of arguments.
Hence, I chose a consistent and logical API over the three functions
together rather than having logical ones per function. Hope it makes sense.
Best,
Frederik
On 28-08-17 21:06, Stanislav Malyshev wrote:
Hi!
additional argument to these three functions. The second implementation
suggestion is to allow an array of options in which all the cookie
options will be moved into. More details are to be found in the RFC.
Something not clear to me on the second one - why lifetime/expiration is
a separate parameter while all others are part of $options?
