I need to recover some values from an application installed on the server side (openssl).
Where are the methods executed? on the server side? on the client side?
Many times I need to use this features/applications from the server side because of de O.S. and because this way the client doesn’t need to install anything.
Is the only way to do it through the headless client?
I mean while headeless client, one license is consummed.
Do the server act like a client?
Do you know another solution besides doing a plugin?
What kind of solutions are you talking about? WebClient or SmartClient?
I think all the methods in WebClient are executed in the server side. If SmartClient does the opposite, it would be very interesting add the feature of execute a method in the server side without wasting a license, something like executeProgram but executeProgramInServer.
Well, I not find very logical that, to access the server S.O. is consumed another license, it is not really a new connection.
On the other hand, I think it should be easier to implement in development time, something like raising Roberto.
As for the plugin, it not will be very difficult to do, but for that reason do not you think that such options should be included in the core of Servoy?
This also opens the door to use the hardware connected directly to the server hardware (modems GSM / GPRS, Fax, Telephone exchanges, etc)
Servoy has tons of great ways to run server-side code. Add headless client (not to be confused with headless_client plugin), REST, stored procedures, and targeting a smart client running on the server to Patrick’s list.
At most, all of these options require one additional license to run server-side code for any number of remote clients. Not sure what the issue with this is given the functionality (assuming you don’t have an issue with Servoy’s licensing schemes in general).
Everything you’ve listed can be accomplished already – and probably several different ways.
with the new enhanced security, you can also run server-side code, without the cost of a license!
use the authenticator solution for that!
the wiki says:
While the security.authenticate(…) function is meant to be utilized in a Login solution, it can be used at any time. This provides an alternative to the Headless Client plugin. The major differences between the two are:
Headless Client plugin starts a Headless Client on the Application Server, that has state and can be used by multiple clients. Method execution is asynchronous.
security.authenticate(…) executes just global methods in a solution of solutionType “Autenticator”, no state is remembered on the server between method calls and the method calls are synchronous
I don’t think so Harjo, for the duration of the execution of the code in the authenticator solution (so a fraction of a second, if you do it properly), a license is consumed.
use the headless_client plugin (works server-side, but uses a license)
use a web client (works server-side, but uses a license)
use a batch processor (works server-side, but guess what? uses a license)
write a plugin (would not use a license)
add this to Servoy core (open a feature request and pray for a bright future)
Now guess which one I would recommend (until the future is brighter)?
I think this “new” feature must be implemented on new Servoy revisions. As Adelo said, it’s very important for our applications the posibility of using many “foreign” programs to complement Servoy capabilities without the need of install anything in our clients.
Just a few examples …
Mail server
Hash, encrypt, sign files and/or strings
Digital signatures of our documents
and many, many other kind of scritps and programs installed on the server side (let’s take the most of Servory in a Linux server …)
I expect that a successful security.login() issued from within the login form consumes one license …
Servoy application server must deny access somewhere when exceeding the user count license…
Regards,
ofcourse, AFTER a successful login, it consumes a license, but I just wanted to know, if you just open the login solution, without really logging in, if THAT consumes a licenses…
Harjo:
ofcourse, AFTER a successful login, it consumes a license, but I just wanted to know, if you just open the login solution, without really logging in, if THAT consumes a licenses…
Harjo,
When js code is running in Servoy, this always runs inside some client (headless, web, smart, authenticator) and this always consumes a license.
So when a client is started, the license is consumed immediately, also before successful login.
I don’t think so Harjo, for the duration of the execution of the code in the authenticator solution (so a fraction of a second, if you do it properly), a license is consumed.
Does that mean, if you have 10 licenses, and 9 are logged in, the 10th can’t be logged in? because his login solution needs a license AND his authenticator needs one (a fraction of a second) or am I seeing bears here?
SO, Paul, now that you have opened up the discussion…
We would like to know what this short time threshold really is?
Can it be exploited to do more than the login? (Not that I would use that of course).
Just want to be clear on the length of time that login can take - if for instance there is a “slow” internet connection.