On 2/12/16 12:46 PM, Aristedes Maniatis wrote:
On 21/01/2016 11:39pm, Dzmitry Kazimirchyk wrote:
>>HttpROPConnector might do with some way to set the cookie name. You made
SESSION_COOKIE_NAME final for some reason.
>
>SESSION_COOKIE_NAME is just the name of the HTTP session header, but having
some sort of pipeline requests go through to be able to add various parameters
like compression, custom cookies, etc. might be beneficial.
A pipeline could be nice, but maybe more work than is needed. A user could just
subclass HttpROPConnector to most of what they want. If SESSION_COOKIE_NAME
wasn't final...
Sorry, not really following... SESSION_COOKIE_NAME is just a string
constant for the default name of the session cookie. Users can still add
any cookies with any names they want by overriding "addSessionCookie" or
"doRequest" method of HttpROPConnector.
Dima
