Any soap webservice demo avaliable?

sonicer · 2016-12-29 07:38:07

I have an apache(v 2.2) dso module(soap webservice), and it works well for more than 10 years.

And recently, the BOSS told me we must upgrade OS to 64bits and update the apache to the latest version(seems 2.4). So sad that the program seems not working on the new server.

I found a standalone webservice demo using Indy, but not sure about the performance.

Is there any soap webservice demo using mormot? I want use mormot in my ported program.

seems lots demo are focus on RESTful, but not the old soap webservice.

ab · 2016-12-29 08:32:10

No, the framework supports only REST (+ JSON), nothing about SOAP or XML.

SOAP is too bloated and slow for our purpose.
Even SOAP is not standard, I've had tremendous incompatibility issues with SOAP services implemented in several technologies (Delphi, Java, C#) on client/server sides.
This is why we did not implement SOAP, and won't.

There is built-in support of SOAP in Delphi. At least SOAP 1.0.
You may be able to just recompile your module using latest Delphi revision.
But perhaps you don't have the time to switch the existing code base to Unicode...

I suspect your BOSS has to understand that upgrading Apache to 64-bit does not make much sense, and will definitively cost a lot.
You can upgrade the OS to 64-bit, but run Apache as 32-bit service, keeping your existing module.

sonicer · 2016-12-29 08:55:10

Thanks for your reponse!

I'll try to explaing the status/statution of our old program to the BOSS.

Thanks again for your great job.

smile · 2016-12-29 12:42:51

> Even SOAP is not standard
WOW!
I don't know the technology having more than standards.
Another thing is that not all libraries support it standards.

SOAP overengineering, is the fact.
It not quickly, but is standardized.
More then one serialization format.
More then one transport layer.
In real life, everything is limited XML/HTTP.
As a result, this is Enterprise Level solution.

Realization of SOAP in Delphi is based on WebBroker.
If somebody writes provider for WebBroker who will use HTTP.SYS as HTTP stack layer, it will be the decision.

We can use SOAP(and any WebBroker) with Indy as Self Hosted Server App/Service
or ANY WEB server extension module that support Delphi:
CGI/ISAPI/Apache shared module.
FastCGI dont support by Delphi :-( in the box.

>At least SOAP 1.0.
As CLIENT Delphi build-in support SOAP 1.3 in any of serialization scheme (RPC|Document)/(Encoding|Literal).
As Server, in native mode, RPC/Encoded only.
Besides complexity is the reason of it.

The producer of Delphi7 (Borland) wrote in documentation (is inexact):
If you need Document/Literal style - use .NET Delphi version.

RemObject's SDK has support of any SOAP dialect, but everything source code should be rewritten.
Lazarus/FreePascal community can offer WST-WebServiceToolkit, SOAP 1.1 only.

mORMot, on the contrary, proposes the solution, other than SOAP.
Quickly cycle of development.
Big capacity.
...and REST

REST is fast and simple alternative to SOAP.
These are the opposed Worlds.

Last edited by smile (2016-12-29 12:48:37)

ab · 2016-12-29 13:27:05

A few years ago, I was asked to see (I won't tell by whom) if WebBroker may use the HTTP.SYS API.
It may have been possible, but WebBroker appeared so complex and bloated that the benefice of using HTTP.SYS appeared to me as very weak.

RemObject and FPC WST are indeed alternative to Delphi SOAP/WebBroker.
You are perfectly right: SOAP, as a standard, is so difficult to implement that you always find incompatibilities when you use diverse stacks and technologies.
What I meant is that "SOAP implementations are no standard"...
You have to stay on most simple RPC structures possible.

smile · 2016-12-29 14:13:27

I agree.

sonicer · 2016-12-30 01:28:46

Cuz we still have lots of programs using SOAP,
It's hard to ask all our clients to do this or that, "We chagne our server from soap to rest, and you should change your program accordingly"
And a bad(or not a good) news is that we still use webservice in our new projects, using C# WCF instead of delphi.

But I think, if it works, although not so fast, then it still has it's day like a dog, lol.

smile · 2016-12-30 14:21:09

I use SOAP many years... since 2001 and last year too.

Its is standardized.
Self documented.

Each technology there is a place.
It is necessary to know it and to apply.

For REST it is necessary to add Swagger or RAML for documenting.
If this public API, then it is mandatory.

In my opinion, SOAP benefits in stable/conservative systems with public API (Java/NET/BigFatEnterprise :-) .

REST benefits in dynamic programs, with a quickly cycle of development/changes.
After stabilizing - we add documentation.

smile · 2016-12-30 14:28:40

...And I still use Delphi for both :-)
The old friend - is better two new. :-)

mORMot provide many services for programs.
I not use it as ORM, but using many other parts.

Long ago the community (Delphi) didn't receive such good library, IMHO.
In many aspects.

sonicer · 2017-01-05 02:33:04

So...
Nobody try to create a mORMOT based webbroker?

ab · 2017-01-05 08:08:06

As I wrote, I tried and stopped due to webbroker structural inefficiency.

mORMot Open Source

#1 2016-12-29 07:38:07

Any soap webservice demo avaliable?

#2 2016-12-29 08:32:10

Re: Any soap webservice demo avaliable?

#3 2016-12-29 08:55:10

Re: Any soap webservice demo avaliable?

#4 2016-12-29 12:42:51

Re: Any soap webservice demo avaliable?

#5 2016-12-29 13:27:05

Re: Any soap webservice demo avaliable?

#6 2016-12-29 14:13:27

Re: Any soap webservice demo avaliable?

#7 2016-12-30 01:28:46

Re: Any soap webservice demo avaliable?

#8 2016-12-30 14:21:09

Re: Any soap webservice demo avaliable?

#9 2016-12-30 14:28:40

Re: Any soap webservice demo avaliable?

#10 2017-01-05 02:33:04

Re: Any soap webservice demo avaliable?

#11 2017-01-05 08:08:06

Re: Any soap webservice demo avaliable?

Board footer