Joels Wish-list

8 views
Skip to first unread message

Joel

unread,
Sep 29, 2010, 3:02:07 AM9/29/10
to r-node-users
As requested here is my wish-list :)

Main features
1) To be able to run an R script when a user login to R-node. This
should be user specific so one script per user so to say. One more
thing about this is that this script should be set by the "admin" and
not by the user himself.
2) To be able to block commands in an easy way.
3) Admin users, the admin user should have an extra menu or something
to set the options for the users and for how R-node shall behave on
this and that.


Lesser features
*An easier way to add/remove what kind of plots that should work (if
no new more dynamic way is found)
*An easy way to add/remove block commands
(both of the two above could be under the admin menu thingy)


Ill post in this thread if I find more things I want, and if you have
any question or if you want me to explain something in more detail
just ask, or if you have any idea that you just wanna talk about.

Joel

unread,
Sep 29, 2010, 3:38:23 AM9/29/10
to r-node-users
+ Lesser feature
Be able to upload a R script and run it.
This can be done today but its not a strait forward path :).

Jamie Love

unread,
Sep 30, 2010, 4:20:05 AM9/30/10
to r-node...@googlegroups.com
Thanks a bunch Joel,

These are in my issue/feature tracker - I'll work on them ... well, when I get time.

Jamie
--
Jamie Love
Looking for custom software development? Contact us at www.nsquaredsoftware.com.

Joel

unread,
Oct 1, 2010, 4:56:24 AM10/1/10
to r-node-users
+ lesser feature

Somekind of indicator that an session is out, or perhaps a count down
somewhere.
Becouse right now it dossent say anything that indicate that your
session has expired and you just sit there and wonder why nothing
happens when you type in R commands.
Or it gives this:

> y<-c(1,2,3)
unknown unknown (403: Forbidden)

Witch aint that easy for a person that dossent have the server log as
well to figure out whats happend...

//Joel

Jamie Love

unread,
Oct 1, 2010, 8:09:41 AM10/1/10
to r-node...@googlegroups.com
I think I'll call this one a bug. It should ask for the password/username.

Also there are two timeouts:

1/ the user's login timeout
2/ the connection to R timeout

currently they're both set to 30 (minutes) in the configuration file. The second timeout should be a while longer.

You can of course alter the timeout to suit you better - setting to 4800 would get people through a whole day.

Jamie

Jamie Love

unread,
Oct 4, 2010, 5:37:01 AM10/4/10
to r-node...@googlegroups.com
Hi Joel,

I've fixed this. Users now get requested to log in again on a 403 error, and their command is rerun. This is best used in conjunction with idleSessionTimeout set to a very long value.

Regards
Jamie

On Fri, Oct 1, 2010 at 9:56 PM, Joel <joll...@hotmail.com> wrote:

Joel

unread,
Oct 5, 2010, 5:11:54 AM10/5/10
to r-node-users
This is more a question then a request but can you put the server to
run as https instead of http somewhere?

Jamie Love

unread,
Oct 5, 2010, 5:14:20 AM10/5/10
to r-node...@googlegroups.com
Not right now.

When I first developed it, nodejs didn't support https (or at least, it was hard and I didn't want the pain).

Supporting HTTPS requires a whole lot of setup of SSL, and will require development to do so.

You can instead proxy through a server such as apache to get https, if it is really important at this stage.

Jamie
Reply all
Reply to author
Forward
0 new messages