[JIRA] Created: (MYO-59) Implement scripting support within the connector

[Robert Hodges (JIRA)]

Implement scripting support within the connector
------------------------------------------------

Key: MYO-59
URL: https://forge.continuent.org/jira/browse/MYO-59
Project: Myosotis
Type: New Feature

Environment: All
Reporter: Robert Hodges
Assigned to: Gilles Rayrat
Priority: Critical
Fix For: 0.7


Implement scripting engine support so that users can script actions on SQL requests and results using the extension point feature described in MYO-58. The scripting language chosen should be robust and lightweight such that:

1.) Scripts can execute at or close the speed of Java methods.
2.) Resource usage by the scripting engine is low.
3.) Scripts do not incur large per connection or per request performance latency. It would be bad, for instance, if scripting added a lot of latency to creating new connections or handling requests.
4.) Scripts are free from synchronization issues that would prevent effective use of multiple core systems. In particular, the scripting engine should not induce synchronization between otherwise independent connections.
5.) Scripts are free from resource leaks.

One possible way to implement scripts is that each new session starts a scripting scope, so that variables set at login time, for instance, are visible to scripts that run at per-request call-outs for that script.

On candidate for the scripting language is Rhino, which does pretty well in performance test results. See http://www.pankaj-k.net/spubs/articles/beanshell_rhino_and_java_perf_comparison/index.html for an example. I have seen similar numbers elsewhere.

[Gilles Rayrat (JIRA)]

[ https://forge.continuent.org/jira/browse/MYO-59?page=all ]

Gilles Rayrat closed MYO-59:
----------------------------

Resolution: Won't Fix

No need for that feature in the near future

Post by Robert Hodges (JIRA)
Implement scripting support within the connector
------------------------------------------------
Key: MYO-59
URL: https://forge.continuent.org/jira/browse/MYO-59
Project: Tungsten Connector
Type: New Feature
Environment: All
Reporter: Robert Hodges
Assignee: Gilles Rayrat
Priority: Critical
Fix For: 0.7
1.) Scripts can execute at or close the speed of Java methods.
2.) Resource usage by the scripting engine is low.
3.) Scripts do not incur large per connection or per request performance latency. It would be bad, for instance, if scripting added a lot of latency to creating new connections or handling requests.
4.) Scripts are free from synchronization issues that would prevent effective use of multiple core systems. In particular, the scripting engine should not induce synchronization between otherwise independent connections.
5.) Scripts are free from resource leaks.
One possible way to implement scripts is that each new session starts a scripting scope, so that variables set at login time, for instance, are visible to scripts that run at per-request call-outs for that script.
On candidate for the scripting language is Rhino, which does pretty well in performance test results. See http://www.pankaj-k.net/spubs/articles/beanshell_rhino_and_java_perf_comparison/index.html for an example. I have seen similar numbers elsewhere.