SOAP disabled on server (needed for Extension Repository)

SOAP is and stays disabled on the server, and than...

Omolto mentioned it one month ago without any response...
http://www.typolight.org/forum/message/76305.html

There is (was) an alternative to use SOAP througth a class using NuSOAP http://sourceforge.net/projects/nusoap/

Does TypoLight use SOAP 1.2 as he mentioned and is there any other way using the Extension Repository without SOAP or with a SOAP php class alternative method?

Does anyone know there is a (new) NuSOAP script in the make?

I have a few clients that use TypoLight with SOAP and we are moving to a new host that have SOAP disabled and does not want to enable it. There are a growing number of hosts that disable this php extension (SOAP) because of security reasons.

Anyone any idea?

The repository only works with native SOAP of PHP 5.

NuSOAP (like other script implementations also) is not compatible on the API side. The protocol itself is of course the same so you could basically write a server software with PHP native SOAP on one side, and a client using NuSOAP on the other side. You would have to rewrite the repository client software based on NuSOAP therefore, which you are free to do if you have spare time.

Nobody could to date answer why SOAP should be insecure. If a hoster really believs it, how could a no longer developed and supported NuSOAP then be more secure that the native and well maintained version included in PHP's standard? Face the truth, thats just an excuse of hosters to lazy learn the facts and set it up properly.

Btw those scripted SOAP implementations were developed for PHP 4 where SOAP was not available otherwise, and of course it also can no way be compared in speed with the native C implementation of PHP 5.

Thank you for the clarification. The host may not be lazy, it's a cheap one. The have everything except SSH and SOAP.
I'm still trying to figure out if it's worth to pay more for only SOAP and SSH access.

It would be nice if TypoLight comes with a "hack" / an alternative method for using the automated live update and extension repository which are very nice (new) features.

Live update does not use SOAP, so that could work in your case.

True, there is at least one hoster in Germany where SOAP is only included in higher hosting plans.
But a hoster claiming to not enable it for "security reason" is just making a fool out of himself.

Nice that Live Update works, I did'n used it yet.

If there are so less hosters in Germany with SOAP enabled, I hope there will be an alternative available to SOAP Extension Repositories in one of the next versions of TypoLight.

i think using SOAP is a fine choice for this task.

if your hoster does not provide SOAP you are free to install these modules by hand and it will work also very nicely (you just have to copy it in your system/modules/ directory and re-run the install script and update your database). You only have to check that you install the dependencies (if needed).