Forum OpenACS Q&A: Re: proc_name in acs_sc_call

Collapse
3: Re: proc_name in acs_sc_call (response to 2)
Posted by xx xx on 06/28/03 10:06 PM
Thanks fo your reply, but I was wondering where the proc 'lives'. At one time, when debugging, I was trying to find out whether a proc was available. Does it live in the environment or is it stored in a table. Are there other ways to find out the existence, except for [info proc]?

Second, I would like to know where the redirect 'lives'. Which part/procedure of OpenACS redirects the 'AcsSc-proc' to the 'package-proc' (in your example "notes_datasource").

Collapse
4: Re: proc_name in acs_sc_call (response to 3)
Posted by Neophytos Demetriou on 06/29/03 11:00 AM
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

Collapse
5: Re: proc_name in acs_sc_call (response to 4)
Posted by xx xx on 06/29/03 08:29 PM
Now it's clear Neophytos, thanks a lot.