mORMot Open Source

Hello Arnaud!

Thank you for your reply. Yes, it is secured in the original source code. I am a proponent of the concept of inherent security when writing functions. The example source code is just reduced to an absolute minimum so as not to violate the forum rules. I had the VariantsToArrayOfConst function in mind. I should have mentioned it, the source code is not the original production code but just an example of behaviour I don't understand.

With best regards
Thomas

I have made the source code for the article example compilable with Delphi7. It can be downloaded from this post.

With best regards
Thomas

Perhaps this example will help you. Take a closer look at function TCustomServiceObject.GetSessionUserDirName.

With best regards
Thomas

No. That is why you can write:

var
  v: Variant;
  isPeaPuree: Boolean;
begin
  isPeaPuree := _Safe(v).O_['One'].O_['Two'].O_['Three'].B['IsPeaPuree'];
  ShowMessage(IsPeaPuree.ToString(TUseBoolStrs.True));

You can easily reproduce the problem with the Init function. Switch on ReportMemoryLeaksOnShutdown. Write the following:

var
  names: TRawUtf8DynArray;
begin
  names := ['one', 'two'];
  names := Nil;

Set a Breakpoint at names := Nil. When you have reached this point during debugging, press Ctrl+Alt+D and open the disassembly window. Now you can see that the compiler has automatically inserted a call to DynArrayClear for this Nil assignment. However, if you write Pointer(names) := Nil, this does not happen and the dynamic array can no longer be cleaned up at the end. In this case, FastMM will report the lost memory.

With best regards
Thomas

Maybe this article will help you.

With best regards
Thomas

You must follow the link in the announcement. I write my posts in Delphi-Praxis Forum.

With best regards
Thomas

You don't read the answers to your questions carefully. You're making it difficult for everyone here to help you. You have already received useful links for the start in post #2. Have you studied this example, which only uses an HTTP server? Once you have found the entry point, you can search the mORMot source code for it and quickly find the answer to your questions. This example only uses a REST server and shows the use of the ORM. These two examples (here and here) show how REST and HTTP servers work together without using the ORM. Why should it be necessary to expose access to the ORM? Use TRestServerFullMemory as Main and only open access to the ORM in the interface-based services. You can combine everything and have already been shown how to do it here. Please let us help you too. Read through the tips you have received again.

With best regards
Thomas

uses
  mormot.core.base,
  mormot.core.data,
  mormot.core.os,
  mormot.net.client;

var
  content: RawByteString;
begin
  content := HttpGet('https://tile.openstreetmap.org/10/549/339.png');
  if content <> '' then
    FileFromString(content, ChangeFileExt(ExeVersion.ProgramFileName, '.png'));

With best regards
Thomas

You can find posts on this topic in this forum.

type
  TCustomServiceObject = class(TInjectableObjectRest, ICustomService)
  protected
    function InternalAdd(const pmcItem: TOrmCustomRecord; pmForceID: Boolean = False): TID;
  public
    function GetDBDataRestServer: TRestServerDB; overload;
    function GetDBBlobRestServer: TRestServerDB; overload;
  end;

function TCustomServiceObject.InternalAdd(const pmcItem: TOrmCustomRecord; pmForceID: Boolean): TID;
var
  restServer: TRestServerDB;
begin
  restServer := GetDBDataRestServer;
  if (restServer <> Nil) and (pmcItem <> Nil) then
    Result := restServer.Server.Add(pmcItem, True, pmForceID)
  else
    Result := -1;
end;

function TCustomServiceObject.GetDBDataRestServer: TRestServerDB;
begin
  with TRestAdminServer(Server) do
    Result := RestServerPool.FindRestServer(GetDBDataRestServerID(ServiceRunningContext.Request.Session));
end;

function TCustomServiceObject.GetDBBlobRestServer: TRestServerDB;
begin
  with TRestAdminServer(Server) do
    Result := RestServerPool.FindRestServer(GetDBBlobRestServerID(ServiceRunningContext.Request.Session));
end;

With the technique shown above, you can also manage several separate databases for each organization without any problems. If you only want to use several databases, you do not need a pool and can access them directly. Then the following is enough:

type
  TServerMain = class(TSynPersistent)
  private
    FHttpServer: TVGSHttpServer;
    FDBDataRestServer: TDBDataRestServer;
    FDBBlobRestServer: TDBBlobRestServer;

With best regards
Thomas

Commit 7267 tested and it works. Thank you very much and have a nice weekend.

With best regards
Thomas

Read this article to find out more about DocVariant. The help describes how the properties are mapped.

With best regards
Thomas

Unit mormot.rest.server
ServiceRunningContext, or better use TInjectableObjectRest for Interface-based Services.

With best regards
Thomas

Sorry Arnaud, I made a stupid copy-paste mistake. Everything is fine with mORMot. The nasty thing was, the Delphi debugger totally misled me. I shouldn't work until the middle of the night. The only good thing was that I got some new ideas from all the debugging. Sorry again for the false alarm.

With best regards
Thomas

In SQLite version 3.38.0 or higher, it can be queried using the following SQL syntax as described in this article (near the end).

With best regards
Thomas

No, you can specify server URI and port and set up several Rest clients as required.

Generally: How you organize your data is up to you. You can have one or more databases for all customers, or one or more databases for each customer. The interfaces only do your routing and the necessary administration. What happens in the background afterwards is up to you. Example: Access via a pool of servers would be:

function TCustomServiceObject.GetReportRestOrm: IRestOrm;
begin
  with TAdminRestServer(Server) do
    Result := RestServerPool.FindReportRestServer(GetReportRestServerID(ServiceRunningContext.Request.Session)).Orm;
end;

function TReportService.UpdateSource(const pmcRowID: TID; const pmcSource: RawBlob): Boolean;
var
  orm: IRestOrm;
begin
  orm := GetReportRestOrm;
  if orm <> Nil then
    Result := orm.UpdateBlob(TOrmReport, pmcRowID, 'Source', pmcSource)
  else
    Result := False;
end;

Here you fetch the corresponding RestServer via a SessionID. The data can come from wherever you want. It can also be another service, created by you or by an outside service provider.

PS: My examples are simple to get started, but can also be easily expanded.

With best regards
Thomas

You can register several services for one RestServer and one root name:

function TXRestServer.InitializeServices: Boolean;
begin
  Result := (ServiceDefine(TX1Service, [IX1], sicSingle) <> Nil);
  Result := Result and (ServiceDefine(TX2Service, [IX2], sicClientDriven) <> Nil);

You can register several RestServers for one HttpServer and port:

FHttpServer := TRestHttpServer.Create(pmcPort, [FXRestServer, FYRestServer], '+' {DomainName}, useHttpSocket);

Depending on the root name for a RestServer, it could look like this (example: root for X-RestServer is "store" and for Y-RestServer is "admin"):

domain.com/store
domain.com/admin

With best regards
Thomas

Only "published" properties are serialized. If you want to serialize other properties, you must register your own functions with TRttiJson.RegisterCustomSerializer().

With best regards
Thomas

You are right. It should look like this:

procedure TServerLog.ComputeFileName;
begin
  inherited ComputeFileName;
  FFileName := MakePath([ExtractFilePath(FFileName), StringReplace(ExtractFileName(FFileName), ' ', '_', [rfReplaceAll])]);
end;

With best regards
Thomas

Are you sure? Then all my comments in source code since mORMot1 are wrong:

  // IMPORTANT: First log in and then call ServiceDefine()!
  if not FServerRestClient.SetUser(pmcAdminUsername, pmcAdminPassword, {HashedPassword=} False) then
    Exit(scsErrLoginAdminUser); //=>

  if not InitializeServices then
    Exit(scsErrInitializeServices); //=>
end;

@RaelB: Have you already tried this example?

With best regards
Thomas

I have created a simple unit for this:

uses
  Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System.UITypes, System.Classes,
  mormot.core.base, mormot.core.text, mormot.core.rtti, mormot.core.log;

type
  TRemoteLogging = class(TComponent)
  strict private
    FLogClass: TSynLogClass;
  protected
    const
      DEFAULT_PORT = 8091;
  public
    destructor Destroy; override;
    procedure Start(pmLogClass: TSynLogClass; const pmcUri: RawUtf8 = '127.0.0.1/LogService');
    procedure Stop;
  end;

implementation

uses
  mormot.net.sock,
  mormot.rest.http.client;

destructor TRemoteLogging.Destroy;
begin
  Stop;
  inherited Destroy;
end;

procedure TRemoteLogging.Start(pmLogClass: TSynLogClass; const pmcUri: RawUtf8);
var
  uri: TUri;
begin
  if pmLogClass <> Nil then
  try
    FLogClass := pmLogClass;
    uri.From(pmcUri, Int32ToUtf8(DEFAULT_PORT));
    TRestHttpsClient.CreateForRemoteLogging(uri.Server, pmLogClass, Utf8ToInteger(uri.Port), uri.Root);
  except
    on E: Exception do
      pmLogClass.Add.Log(sllError, E);
  end;
end;

procedure TRemoteLogging.Stop;
begin
  if FLogClass <> Nil then
    FLogClass.Family.EchoRemoteStop;
end;

It is used like this:

procedure TfrmMain.FormCreate(Sender: TObject);
begin
  ...
  TRemoteLogging.Create(Self).Start(TSynLog);

With best regards
Thomas

I think you are using a mORMot2 version that was created before May 2022. It would be better to update to the current one. That's all I can help with.

With best regards
Thomas