Generalize.
1. You can have 1 BP/1 BO called GET resource which gets:
And based on that information constructs the required JSON.
2. If BP only proxies requests to BO you can skip BP and call BO straight from BS.
Check out RESTForms2 - it does something similar (CRUD over classes) and there's only 4 handlers for all classes.
If you want to minimize the roles given to a user, use Privileged Routine Applications.
With them, only specific lines of code would have additional privileges, such as %DB_CACHESYS:R.
For community Python Gateway I wrote an $lb -> tuple converter.
You can check it out here. To be callable from Python you can expose it as a Python C extension.
While I do agree, what's the use case?
If you're requesting objects en masse it's usually via sql and it's easy to provide id there.
In a case of a singular object you usually request it by ID so it's known beforehand.
Interesting question!
Here are my findings for store/intersystems/irishealth-community:2020.4.0.524.0 and a simple app in the USER namespace.
| Uncompressed (Mb) | Compressed (Mb) | |
|---|---|---|
| IRIS | 3 323 | 897 |
| IRIS Squashed | 3 293 | 893 |
| App | 8 436 | 1 953 |
| App MSB | 3 526 | 937 |
| App Squashed | 3 576 | 931 |
| App MSB + Squashed | 3 363 | 904 |
Notes:
docker inspect -f "{{ .Size }}" $image(docker manifest inspect $image | ConvertFrom-Json).layers | Measure-Object -Property size -SumConclusion: either MSB or Squashed work fine, but just MSB would be better for storage as it can have shared layers (squash always produces one unique layer). Squashed is easier to implement.
The best place to do that is your REST broker.
After you got your error from BP, just create your own error and pass that.
Can DB made RO for a while?
Check this article.
Doubltul - it requires Java installation or configuration.
Iterating through large pandas dataFrame objects is generally slow
You're right.
Thank you!
Why do you map %ZLANGC00/%ZLANGF00 to %ALL? They are available everywhere by default.
What's a CSP service? A REST service?
What do you want to achieve?
What are the triggers for a session closure?
If that is indeed the case I recommend this series of articles.
Try
set DynObj={}.%FromJSON(filename)What's Quality area?
It's not a server who checks for expiry, but a client. So your flow works like this:
1. 15:00 calling application runs a GET request for patient?MRN=A
2. 15:00 CSP Web application calls HIHLib.REST.Server class and forwards request on to namespace for handling (via business services,process and operations)
3. 15:00:05 response is returned with EXPIRES 300 and VaryByParam set to *
4. 15:10 a seperate internall process results in patient with MRN A - first name changed from pete to bob
5. 15:12 calling application runs a GET request for patient?MRN=A
6. 15:12 web browser (on a client side) sees that patient?MRN=A request is cached locally and still valid due to EXPIRES 300. Web browser is returning a cached value to a calling application without going to the server.
And server would never get a second request (that's the point of the EXPIRING header after all).
Expires controls how long the response is valid. It's for things like HTML pages which are static.
If you think that a response can change every time a client requests it, you should not add an EXPIRING header.
Sorry, meant:
Do ..Adapter.%Client.SetHttpHeader(name, value)Call:
set sc = ..Adapter.SetHttpHeader(name, value)Calling @Benjamin De Boe
If you want to know if a compiled class exists, call:
write $$$comClassDefined(class)It, however, does not answer the question of a compiled version being current.
Depends on what WS expects, really.
SELECT 1How about a slightly different architecture:
Requests - and from Data Source namespace add 1 row to it on every new message.Ack which contains {RequestId, Namespace, State}Requests/Ack tables to get new unprocessed requests (no corresponding Ack record).Ack record and send a message in a local namespace for BP processingAdvantage of this architecture is that you decouple processing on a namespace level - so if a production in one namespace is in error state/down the rest can proceed. It also eliminates a single point of failure in namespace switching job.
tl;dr instead of pushing your event make consumers pull it whenever convenient.
Supply them in $horolog format. In a case of YYYY-MM-DD, try: $zdateh("YYYY-MM-DD", 3)
You can also just call:
set jsoninput = {}.%FromJSON(dir)where dir is a filename.
Use any of the Binary streams:
To send a stream just fill EntityBody property of a request object by calling it's CopyFrom method.