RDi is Java and integrates with JT400. That isn't much of an option with VSCode, so SSH it is.
Jack Woehr
Independent Consulting Programmer
[icon] 303-847-8442<tel:303-847-8442>
[icon] jack.woehr@xxxxxxxxxxx<mailto:jack.woehr@xxxxxxxxxxx>
[icon] www.procern.com<
https://www.procern.com>
[icon] Stay Connected!<
https://www.linkedin.com/company/procern-technology-solutions/>
[photo]
Not Just MSP, We Also MSSP.<
https://procern.com/cyber-security-managed-services/>
NON-DISCLOSURE NOTICE: This communication including any and all attachments is for the intended recipient(s) only and may contain confidential and privileged information. If you are not the intended recipient of this communication, any disclosure, copying further distribution or use of this communication is prohibited. If you received this communication in error, please contact the sender and delete/destroy all copies of this communication immediately.
[__tpx__]
________________________________
From: OpenSource <opensource-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Charles Wilt <charles.wilt@xxxxxxxxx>
Sent: Monday, April 28, 2025 07:32
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxxxxxxxx>
Subject: Re: [IBMiOSS] Why does VS Code for i require SSH when RDi doesn't?
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
AFAIK, RDi doesn't use any non-public API's or Services..
I suspect it's simply that VS Code already supported "remote" systems via
SSH.
Since the i has SSH, it was simpler to use that rather than a whole other
set of calls.
Charles
On Fri, Apr 25, 2025 at 1:04 PM David Gibbs via OpenSource <
opensource@xxxxxxxxxxxxxxxxxx> wrote:
IIRC: RDi uses system API's to interact ... when VS Code was created, I
don't think Liam had access to those API's.
david
Jack Woehr
Independent Consulting Programmer
303-847-8442
jack.woehr@xxxxxxxxxxx
www.procern.com
Stay Connected!
Not Just MSP, We Also MSSP.
NON-DISCLOSURE NOTICE: This communication including any and all attachments is for the intended recipient(s) only and may contain confidential and privileged information. If you are not the intended recipient of this communication, any disclosure, copying further distribution or use of this communication is prohibited. If you received this communication in error, please contact the sender and delete/destroy all copies of this communication immediately.
midrange.com
