Aldert, upon startup, the acs-service-contract looks into the available bindings (contract <--> implementation) in the db and foreach operation in the service contract it *generates* a proc of the form AcsSc.${contract}.${operation}.${impl}.
That proc is nothing more but a redirect to the concrete/actual implementation (provided by ${impl}) of the abstract contract operation. Check out the following url that is the API documentation of the **autogenerated** proc for the redirection for the operation ''datasource'' of the
service contract ''FtsContentProvider'' based on the implementation named ''forums_message'':
https://openacs.org/api-doc/proc-view?proc=AcsSc.FtsContentProvider.datasource.forums_message&source_p=1
For more autogenerated procs, check out:
https://openacs.org/api-doc/procs-file-view?path=packages%2facs%2dservice%2dcontract%2ftcl%2facs%2dservice%2dcontract%2dinit%2etcl
