Hi Wathsara, Just a small suggestion, as per the architecture you are having only one launcher (web socket launcher). What if we have an STDIO Launcher implementation as well (If it is a valid use-case) and the user can use the stdio launcher when using the plugin locally?
Cheers, On Mon, Oct 14, 2019 at 3:06 PM Wathsara Daluwatta <[email protected]> wrote: > Hi all, > > We have started to implement the Language server support for Identity > Server. This will enhance the developer's experiences of IAM artifacts like > service providers. It will help Dev, QA, to design and see the artifacts > easily. Initially, we are building a VScode extension that is going to > support the adaptive authentication scripts of the WSO2 identity server. > > A language server for adaptive authentication scripts is been implemented > in Java (Server-side). Then the language server and the vscode plugin will > be communicated via WebSocket. > The reason why we selected the WebSocket is to connect the IDE (vscode) > with the IAM server, local, on-prem, in a remote server or in the cloud. > > I have attached the high-level architecture as well. > > Wathsara Daluwatta | Intern - Engineering | WSO2 Inc. > > (m) +94717005121 | Email : [email protected] <[email protected]> > > [image: https://wso2.com/signature] <https://wso2.com/signature> > > -- *Nadeeshaan Gunasinghe* Associate Technical Lead | WSO2 Inc. mobile: +94770596754 email: [email protected] in: https://www.linkedin.com/in/nadeeshaan
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
