We are obviously long past the time when the web itself is new, and we've all watched and even participated in the birth and almost-death and, perhaps, the almost-not-death of XPages.
Net, and other applications can access IAM directly through IAM's RESTful APIs. node-iam-client : A Node.js module to assist your Node.js application to talk with IAM.oauth-dsapi-extension : A Domino extension to enable Domino to trust IAM and consume tokens that IAM grants to your application.domino-iam-service : A Node.js based lightweight server, which is deployed along with a Domino server to provide the whole IAM service.I don't know a heck of a lot about how it works, but it has three components: IAM - This is an authentication piece which allows for OAuth 2.0 scopes to be authenticated to user ids in the ID Vault (or locally on the server?).The former lets you know the status of a bulk operation while the latter lets you know a bit about what went wrong when something did go wrong. The BulkResponse class and DominoDBError class are both encapsulated ways to hand back information on the results of an action.This is a parallel to the NotesDocument class in LotusScript, and has seven methods for accessing, replacing, and deleting items and attachments. The Document class is created using the useDocument method from the Database class.Most of the methods are for bulk operations based on DQL selections. It has eighteen methods and a couple of other gets for properties.
This is the closest you get to a true class like the NotesDatabase class in LotusScript.
#Lotus notes 10 json code#
domino-db - This is the package which your Node code will reference directly.Then, the DQL is resolved and reads/writes executed and the return value go back to the client. In true client/server fashion, the Node JS stuff from the client is packaged up and sent to Proton.