#1 2012-09-26 11:53:02

h.hasenack
Member
From: Nijmegen, Netherlands
Registered: 2012-08-01
Posts: 173
Website

Mormot Enterprise Manager

COnsidering the fact that it is required to have the interfaces registered at both the clienbt and server side, it seems very hard to create a generic Mormot ORM browser.

Is it possible to create some kind of Mormot enterprise manager, or mormot explorer that allows browsing and investigation of interfaces and (virtual) tables provided by an arbitrary mormot server?

I think it would be a very welcome addition to the mormot framework to have this kind of "enterprise manager".

Hans

Offline

#2 2012-09-26 14:54:31

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,660
Website

Re: Mormot Enterprise Manager

Interface signatures can be exported optionally from the server side.
By default, only a hash is transmitted, to allow a quick check of the both side interface coherency.

A "mORMot service browser" may be implemented, using this interface signature feature (which supply JSON content).
A service catalog system should be also implemented.

But the current use pattern is to define interface in code, and to share the interfaces within both client and server sides, in conjunction with the common TSQLModel.

A WSDL gateway could be a good idea: not reinventing the wheel, be allow to expose some services as regular SOAP, for third-party consumption.
I guess this is not a simple task, due to the SOAP message-based architecture, and the fact that I'm no SOAP expert, nor that we do not need this feature yet.

Interesting perspective, indeed...

Offline

#3 2012-09-27 09:10:49

h.hasenack
Member
From: Nijmegen, Netherlands
Registered: 2012-08-01
Posts: 173
Website

Re: Mormot Enterprise Manager

SO no priority here wink
Maybe we could define a standard "interface query" interface which allows querying the # of interfaces, an enumerator returning the hashes of the available interfaces, and next an interface quary wich returns the interface name and  GUID, as well as (named) methods and properties. None of this would have to be SOAP, but could be provided through the regular JSON/Mormot interfaces.

Offline

#4 2012-09-27 12:08:14

mpv
Member
From: Ukraine
Registered: 2012-03-24
Posts: 1,571
Website

Re: Mormot Enterprise Manager

I plan to implement such functionality in my mORMot-based project in few weeks for use with Ext.direct ( see https://www.sencha.com/products/extjs/extdirect and one of Delphi realization here: http://code.google.com/p/extpascal/). So I do it and share code here - I think this is what we need. About SOAP: in my opinion SOAP is very "hard" for our little mormot smile In today world, even on enterprise level, SOAP became not popular. I know some big J2EE project used JSON-RPC instead.

Offline

#5 2012-09-27 13:57:22

h.hasenack
Member
From: Nijmegen, Netherlands
Registered: 2012-08-01
Posts: 173
Website

Re: Mormot Enterprise Manager

jay - that sounds great! (waiting impatiently)

Offline

#6 2012-09-27 15:17:23

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,660
Website

Re: Mormot Enterprise Manager

yes... definitively a nice idea!

I'm not a big fan of SOAP message layout either.
Our implementation is very close to JSON-RPC, and could be adapted if needed.

Offline

Board footer

Powered by FluxBB