Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.6
-
Fix Version/s: None
-
Component/s: LAMS
-
Labels:None
-
Environment:All
-
Database:Any
-
Affected Branches:MOODLE_16_STABLE
Description
LAMS module directly includes lib/soap/nusoap.lib effectively bypassing the php5 soap functions. I was under the impression that the plan was for all soap clients/servers in Moodle to call the wrapper lib/soaplib.php
I as because I am about to extend the functionality of these wrappers and don't want to wreck anything !!
Activity
- All
- Comments
- History
- Activity
- Source
- Test Sessions
From Ernie Ghiglione (ErnieG at ee.usyd.edu.au) Thursday, 4 May 2006, 07:04 AM:
I was under the impression that we were doing this after 1.6 was released. Have you changed this? If so, what's the deadline we are looking into now?
From Martin Dougiamas (martin at moodle.com) Thursday, 4 May 2006, 12:13 PM:
Howard, can you please discuss the soap changes before embarking on them.
From Howard Miller (howard.miller at udcf.gla.ac.uk) Thursday, 4 May 2006, 04:48 PM:
Ernie - yes, absolutely no changes in 1.6. Will be in 1.7dev. Sorry, has there already been a decision on this? I didn't realise.
Martin - absolutely yes. BUT intention is that these will be to expose additional functionality in the underlying libraries so that servers can be written. Everything in soaplib.php should be backwards compatible with existing code.