Changes

Sugar Services makes sense only for activities that have non Sugar Platform dependencies and support more then one Sucrose release cycles.

Sugar Services makes sense only for activities that have non Sugar Platform dependencies and support more then one Sucrose release cycles.

For such activities focus is shifting from Sucrose to API of services they are using. More over activity could be stuck to particular service API version(of course if service developers still support this branch) and Sugar Services will support many branches for the same service simultaneously.

For such activities focus is shifting from Sucrose to API of services they are using. More over activity could be stuck to particular service API version(of course if service developers still support this branch) and Sugar Services will support several branches for the same service simultaneously.

To utilize services benefits, activity developer just need to add xml file with all services that activity uses and(if activity targeted to sugars w/o [[Features/Zero_Install_integration|Zero Install integration]]) startup pure python library to initial launch of Services infrastructure.

To utilize services benefits, activity developer just need to add xml file with all services that activity uses and(if activity targeted to sugars w/o [[Features/Zero_Install_integration|Zero Install integration]]) startup pure python library to initial launch of Services infrastructure. Services infrastructure will provide specified services(and specified versions) for activity and will export environment variables, like LD_LIBRARY_PATH or PYTHONPATH, to activity session, so activity developer shouldn't adapt code to Services.

=== Service developers ===

=== Service developers ===