opus wrote: > Javascript is anything but procedurally, and I think it works pretty good > for what it needs to do -- have you tried to write any applications in > res_js yet? I'm sure you will be very impressed. The key is to integrate > res_js with odbc, or you can do something similar with hash tables and > FetchURL (another anthm invention) > > Some things that could be added to res_js; sql, async originate, swig > interface to libopenpbx, etc. recently there was a res_js dbput/get patch.
Hmmm, I think Javascript is kind of in that grey area between OO and procedural - you can use it either way. Anyway, the main points I'm concerned about are, is Javascript going to be the dialplan language of choice in OpenPBX, and is it going to be integrated at the core, or just another abstraction layer that resolve JS to native Asterisk-like dialplan instructions? Using dbput/get will be an important feature for apps like voicemail that should store user preferences (such as whether to read the date/time of messages - a feature that's pretty standard in a lot of voicemail systems). _______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
