I’m with Anton here. I don’t think [exit] within a Rivet interp should be possible. It’s just not something you should be doing, and in almost all cases, you’re not doing what you think you’re doing.
I learned this hard lesson back in the NeoWebScript days. I would call [exit] to terminate serving the page, and it worked! It worked exactly like I hoped it would. What I didn’t understand was that I was causing the entire child to exit. Of course I was. I just didn’t know it because I hadn’t thought it through. Most of the time when you want to exit a Rivet request, what you really want is to just stop serving the request and bail. But going to all the trouble to exit the interp and kill off the child in the proper way sounds unnecessary. D > On Sep 11, 2015, at 12:51 PM, Anton Osennikov <[email protected]> wrote: > > 11.09.2015 14:18, Massimo Manghi пишет: > >> Then, in order to mitigate the possible interpreter >> termination/initialization storm that might ensue an inappropriate usage >> of the 'exit' command > > But what's the known *appropriate* usage of the 'exit' command inside rivet? > > If there isn't one, maybe just code something like > > ### > > rename exit _exit > > proc exit {args} { > error "application error: 'exit' called inside (threaded) Rivet application" > } > > -- > Best regards, Anton. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
