Hey, my 2 cents here, what I see from VS Code and IntelliJ there collaborative Features. They hosted smth on the web. VS Code uses GitHub I think for contributing and IntelliJ also has a host for this. So I think this. It is not About chatting it is About pair programming: https://visualstudio.microsoft.com/de/services/live-share/ and https://blog.jetbrains.com/de/blog/2020/10/01/code-with-me-eap/ unfortunately both are not open source also the VS Code stuff not, but it seems that it would be better to handle this with like a rest API and not with sockets etc.
Cheers Chris Von: Will Hartung Gesendet: Donnerstag, 28. Januar 2021 06:39 An: dev@netbeans.apache.org Betreff: Re: Collaborative Editing with Netbeans On Wed, Jan 27, 2021 at 2:08 PM Eric Bresie <ebre...@gmail.com> wrote: > I was wondering if it was possible to embedded a “jabber server” as part > of it, then the host (of the session) would fill the roll of the server. > Not saying this wouldn't be useful, but, especially in today's world of remote development, not ideal. The simple problem is it's difficult for most people to open up ports and get them routed to the world wide internet. Machines sharing a common network don't necessarily have this problem. Perhaps machine sharing the same corporate VPN network may not have this problem, but as with all networking, "it depends". So, hosting a server within the tool would probably work for local cases and maybe proof of concept, but in the big picture it's problematic. And hosting a public Jabber server may or may not be a good idea, since it's "just Jabber", nefarious elements may piggy back on it to move traffic you may not like. It should be straightforward for a company to set up a Jabber server and credential it properly for their employees. OpenFire is an Apache Licensed Java XMPP server. I think my company has used it in the past, so it at least functioned at a fundamental level. We didn't do much with it as I recall. Should be straightforward for whoever publishes the team add-ons to have instructions for using something like this, even publish docker scripts with instructions on standing one up on a cheap cloud service. But managing this at the Apache level, as some kind of public service, seems too much to ask. Regards, Will Hartung
