Re: Use cases for local-end set session id?

The main use case I have is instances where you want to be able to restart
the browser but maintain the same session id so that we can debug problems
easier from logs. This has been implemented like that in Gecko for the
Firefox Hello and Firefox Desktop automation teams.

There might be other times where we want to be able to debug session
details being moved from point  to point and put our own session id so that
it might be easier to follow. This would be useful with things like
Selenium Grid.

I would be happy to change to present with a string or have it missing in
the spec.

David

On 4 February 2015 at 18:32, James Graham <james@hoppipolla.co.uk> wrote:

> What's the use case for local ends requesting a session id? As far as I
> can tell from the spec at the moment, the local end and all
> intermediaries have to deal with the possibility that the remote sets
> its own session id that's different from the requested one. Therefore
> this feels like a feature that adds a lot of implementation complexity
> and high possibility for bugs (e.g. because code assumes that it will
> always get the session id it requested, but doesn't), but has little
> value since it can't actually be relied on. Therefore my a-priori stance
> is that it should be removed.
>
> If there are compelling use cases for it it should at least be
> simplified to "present with a string value" or missing, and not allow
> null or anything else.
>
>