Could someone, who has back end Rserve set-up, please, verify that the following chunk of code (two calls back to back) produces 2 identical values of data.reportSessionId variable ?
LABKEY.Report.createSession({
failure: onFailure,
success: function(data){
console.log( 'reportSessionIdCreate: ' + data.reportSessionId );
}
});
LABKEY.Report.createSession({
failure: onFailure,
success: function(data){
console.log( 'reportSessionIdDelete: ' + data.reportSessionId );
}
});
If in your case, it does not, then any pointers regarding why mine does are appreciated...
Thanks. |
| |
| Dax responded: |
2013-04-11 16:48 |
I can repro this and will investigate further. Turns out you don't need an rserve running, just turn the experimental feature on. Note that when the feature was turned off, I did get two server-side exceptions which indicates that createSession was called twice when running the above code. |
| |
| Leo Dashevskiy responded: |
2013-04-11 16:50 |
So the session id generation is done along side the actual creation of a session and does not depend on the latter to succeed first? |
| |
| Dax responded: |
2013-04-11 17:04 |
Correct. The reportSessionId is just an identifier for an underlying R connection. The connection isn't actually created until report execution time. |
| |
| Leo Dashevskiy responded: |
2013-08-02 12:47 |
For Windows 7, Chrome version 28.0.1500.95 m it seems to work fine, I'll check from the office on Monday, if it works from Linux... |
| |
| Leo Dashevskiy responded: |
2013-08-07 14:56 |
Chrome Version 27.0.1453.93 running under Ubuntu seems to be fine also. Closing it up... |
| |
|
|