Configuring MAP needs to use proxy solutions requiring system proxy, i.e.:
php proxy will slow down web transaction more than cgi/apache proxy but will ease EasySDI configuration for organisms which are not able to manage such system proxy.
Question : php proxy would be the default configuration but the system proxy will remain (as an option) if necessary, right ?
- Target version changed from 134 to 135
The administrator can mange the proxy path in the Map config. The default path could be "component/com_easysdi_map/proxy.php" but if the user wants to use an other one, he can change it.
"Surrogafier" php proxy project (http://bcable.net/project.php?surrogafier) have got nice features and could be integrated to/inspired for EasySDI php proxy...need some common discussion about that...
Thanks to Thomas for proposing such php proxy!
I would suggest to add this discussion to the list of points that have to be discussed within the technical committee.
- Target version changed from 135 to 4.0.0
- Status changed from New to Accepted
- Status changed from Accepted to Affected
- Category set to MAP
- Status changed from Affected to Resolved
"Surrogafier" php proxy has been integrated inside easySDI.
In MAP otions, administrator can define which kind of PHP proxy must be used. If empty, it means that easySDI uses the one which is integrated.
- Status changed from Resolved to To merge
- Status changed from To merge to Closed
Also available in: Atom