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
So Main issue is, when stopping on service which is same name on same port will halt current active service
** Left ** and ** Right ** terminal is activated as same name. But Closing Right Terminal request prevent to browse which is valid but showing active on left is not valid.
The text was updated successfully, but these errors were encountered:
Actually the newer command run (with same service name) always replaces the older service endpoint. Older local service does not recieve any further requests.
There are 2 possible options I currently see to resolve service name conflict:
Replace older service with newer local endpoint and terminate old processes running in that name
Disallow users to execute new process with service name conflict
I see option 2 to be a better option but I want to give this a bit more thought before implementing. Till then I will keep this issue open.
ported using same name on same port
Results
No issues on browsing..
Ported Using different name on same port
Results
So Main issue is, when stopping on service which is same name on same port will halt current active service
** Left ** and ** Right ** terminal is activated as same name. But Closing Right Terminal request prevent to browse which is valid but showing active on left is not valid.
The text was updated successfully, but these errors were encountered: