Juha,
I've updated the documentation. I don't know how to produce output, so I don't know if it works. I haven't done a patch before either, so, let me know if this is the preferred format or if you want to see it a different way.
By the way, when I was reading the documentation I noticed that the enum query puts the highest priority query in the ruri, then the rest of them are stored in new branches with a q value.
I haven't actually tried this. Is it the plan that these branches will be looped through serially upon failure without having a retry route block?
The new patch is attached.
Thanks, -g
On Jan 29, 2006, at 4:27 AM, Bogdan-Andrei Iancu wrote:
To be more precisely, the file is modules/enum/doc/enum_user.sgml
bogdan
Juha Heinanen wrote:
is the documentation the README file?
you have to edit the xml file from which README is generated automatically.
-- juha
Hi Greg,
the patch is on cvs! please all see my inline comments.
Thanks, bogdan
Greg Fausak wrote:
Juha,
I've updated the documentation. I don't know how to produce output, so I don't know if it works. I haven't done a patch before either, so, let me know if this is the preferred format or if you want to see it a different way.
By the way, when I was reading the documentation I noticed that the enum query puts the highest priority query in the ruri, then the rest of them are stored in new branches with a q value.
I haven't actually tried this. Is it the plan that these branches will be looped through serially upon failure without having a retry route block?
if more than one entries are returned, by default parallel forking will be performed. For a serial approach, please see the core serial forking support that have been introduced in the devel version. See http://www.openser.org/pipermail/devel/2005-November/001244.html
The new patch is attached.
Thanks, -g
On Jan 29, 2006, at 4:27 AM, Bogdan-Andrei Iancu wrote:
To be more precisely, the file is modules/enum/doc/enum_user.sgml
bogdan
Juha Heinanen wrote:
is the documentation the README file?
you have to edit the xml file from which README is generated automatically.
-- juha
Greg Fausak writes:
I don't know how to produce output, so I don't know if it works.
command is docbook2txt file.sgml.
I haven't done a patch before either, so, let me know if this is the preferred format or if you want to see it a different way.
you should make patch with command "diff -c". the best way is to do it recursively on the original lcr directory and your modified one.
I haven't actually tried this. Is it the plan that these branches will be looped through serially upon failure without having a retry route block?
yes, you can do that for example using lcr module load_contacts()/next_contacts() functions.
-- juha
Hello,
On 01/31/06 05:10, Juha Heinanen wrote:
Greg Fausak writes:
I don't know how to produce output, so I don't know if it works.
command is docbook2txt file.sgml.
FYI: the Makefile has different target commands to generate the documentation. You need to install docbook-utils package and then to update the readme of lcr module, use:
make modules-readme modules=modules/lcr
More details here: http://openser.org/dokuwiki/doku.php?id=openser_modules#module_documentation...
Cheers, Daniel
-
Bogdan-Andrei Iancu -
Daniel-Constantin Mierla -
Greg Fausak -
Juha Heinanen