Forum OpenACS Q&A: Re: Using the API for shell scripts
Welcome to the community!
Have you looked at the batch synchronization?
If you have the possibility of fitting the users into a big XML document following the IMS Enterprise 1.1 specification for user information, we can load it into .LRN automatically.
The documentation is still a bit short of perfect:
Visit /acs-admin/auth/ on your server to work it.
If you need anything explained, just post here.
Thanks for the reply.
That is a nice tool!
But I need some thing more flexible, for
calling from command line (linux bash).
I am looking the code for call tcl procs that
I need but I have found that several tcl used code is
embebed in aolserver (like nsv_array structure)
and I do not know how could I use that
from my program (it is programed in C).
All the way, I think of OpenACS would need full
independence from aolserver code. In that way we
could build tools for administrate since command
I think the following is not useful for Jose's application, but just in case:
If on the other hand you're writing an AOLserver module in C, you may have noticed that AOLserver provides no C API to nsv, only a Tcl API. However, it is fortunately not too difficult to add an efficient C NSV API. I have done so and use it myself, although I never packaged it up for release. (Which means if someone actually needs it, let me know.)
If you are writing a non-AOLserver multi-threaded program and miss the AOLserver Nsv API, you are in luck, just use the Tcl Threads Extension with tclsh. It's tsv api is just like nsv only better. Last time I looked tsv also has only a Tcl API no C; I never tried to add a C API to it but presumably it should also be feasible.