Remote scripting - an interface, add or functionality?

Hi, 

I am a student at NTNU and I am currently working on a preparation project for my master's thesis about Plaxis remote scripting and Python, and I have a couple of questions regarding remote scripting. 

  • I am not sure how i should refer to "remote scripting". Is remote scripting an interface, a functionality or an add-in? For example:  "Plaxis remote scripting is an add-in/a functionality/an interface/a technology that enables ...".  What is correct? 
  • I also have a question about the API and Plaxis remote scripting. Does the API enable remote scripting, or is remote scripting one kind of API? I have pasted some information I found about this on Bentley Systems' web pages, but I still don't get how remote scripting and the REST HTTP API is "connected". I do not have a lot of knowledge about programming and I am having a hard time understanding this. 

The PLAXIS software provides an HTTP based API (REST HTTP API), for which a special Python wrapper was developed for an easy to use scripting API. Both PLAXIS Input and PLAXIS Output support this usage of a Remote Scripting server. 

Best regards, 

Dina Hansen

Parents Reply Children
No Data