Forum OpenACS Development: Re: xotcl core cr procs throw out assigned item_id and assign a new one, why?

I think what is desired is to be able to pass in the id of the object to be created, AND have the code that creates the object use that id.

Every proc that creates a new object accepts the new object ID parameter; if it's an id, you have the id to create the object on, if it's null, you generate a new id.

The main reason I use that feature, is to implement double-click protection; the "add new whatever" form would have a generated ID as a hidden field, and if the OK button was hit twice, you would not get two objects, two copies of a forum posting, two credit card charges.