Skip to content

Index

DQL Explorer and Domino

A couple of weeks ago I explained that, even though the UI of DQL Explorer is a React app, the use of DQL is in agents. The two key agents, found within the NSF itself are runDQLExplain and runDQLQuery - the purpose of each should be apparent from the name. But the purpose of this blog post is to outline the interaction points between DQL Explorer and Domino.

DQL: What Is It Good For?

tl;dr - anything you're doing on Domino, but the message doesn't seem to have reached everyone.

DQL has been at the forefront of my radar since Domino V10 over a year ago. If I remember correctly, documentation wasn't immediately available in Domino Designer's Help, but was soon published online. It's been at the heart of sessions and advances ever since. It's often been discussed alongside the app dev pack, which allows Node.js applications to interact with Domino via the proton task. And judging from a couple of discussions in different fora over the last week, it appears the connection between DQL and the app dev pack seems a little too close. It seems to have led some to ignore DQL assuming it's only for Node.js development.

Speaking at Engage 2020

Engage 2020

It's just over six weeks until the first user group conference of the year, the always excellent Engage. And I will be speaking again this year, with three sessions.

Travels In Manila

As I sit in the airport awaiting my flights back to the UK, I'm reflecting on a busy and eventful 10 days in Manila. For those not aware, in addition to some global members of the team, the bulk of the HCL Labs technical team are based in Manila in the Philippines. This was my first chance to meet the team in person, as well as my first chance since joining HCL to sit down with Stephan Wissel in person. Those who were at Collabsphere got a sneak peek at what the team has been working on. But with the start of 2020, it's time to ramp up planning for the user groups and factory tours this year, starting with Engage.