So, as I understand it it's currently a combination of Session factoryish and weird surface bits.
create_surface_for looks to be a bit of a hack we should get away from - this is an internal implementation detail that shells shouldn't have to worry about.
handle_surface_created is simply a listener interface that could go elsewhere.
It's somewhat inconvenient that we already have a frontend::SessionCreator. Otherwise that would be a fine name for the first part :).
Yeah.
So, as I understand it it's currently a combination of Session factoryish and weird surface bits.
create_surface_for looks to be a bit of a hack we should get away from - this is an internal implementation detail that shells shouldn't have to worry about.
handle_ surface_ created is simply a listener interface that could go elsewhere.
It's somewhat inconvenient that we already have a frontend: :SessionCreator . Otherwise that would be a fine name for the first part :).