You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The recent changes on #94 / #96 introduce a new constraint, where all clientIds have to be universally unique. ClientIDs are now prefixed with an Application ID.
This may cause some issues in existing applications, and this requirement is a bit too strict, as it introduces random IDs in the GSLP Widget/Client ID.
This was initially required, to retrieve the correct GLSPClient from the clientId, on the server side. However, we now inject the GLSPClient in the DI Container, so this mapping is no longer required. Thus, we can revert to the original behavior, where clientIds simply have to be unique within a single client (i.e. Browser Tab)
This issue is mostly about the Server-side requirement. Clients may still generate/use UUIDs if they want to; but the server shouldn't require it.
The text was updated successfully, but these errors were encountered:
- Remove the clientId to GLSPClient mapping in ClientSessionManager
fixeseclipse-glsp/glsp/issues/109
Signed-off-by: Camille Letavernier <cletavernier@eclipsesource.com>
The recent changes on #94 / #96 introduce a new constraint, where all clientIds have to be universally unique. ClientIDs are now prefixed with an Application ID.
This may cause some issues in existing applications, and this requirement is a bit too strict, as it introduces random IDs in the GSLP Widget/Client ID.
This was initially required, to retrieve the correct GLSPClient from the clientId, on the server side. However, we now inject the GLSPClient in the DI Container, so this mapping is no longer required. Thus, we can revert to the original behavior, where clientIds simply have to be unique within a single client (i.e. Browser Tab)
This issue is mostly about the Server-side requirement. Clients may still generate/use UUIDs if they want to; but the server shouldn't require it.
The text was updated successfully, but these errors were encountered: