I modified the lifecycle
on the server to Invocation. On the client, I modified the property PreserveSessionID
of the component Drestconection for false because I don’t have the need to manage or create sessions. This way in case of unavailability of the server or of link internet once the interruption is resolved the app will be able to redo the connection.
The security routine I use, is applied in two moments, at the time of the creation of the mainform where menus are mounted and during component connection Drestconection where the login and password are passed to access the server methods.
At first it worked I’m doing more tests to reach a final conclusion.
Thank you all for your help.
I’m using Session and it’s behaving like Session, so much so that after a time of inactivity it loses the session and I have to reconnect. Actually I wanted to know what loss I have in using input in my case.
– edmjunio
@edmjunio Basically when using Invocation you create a new instance for each customer invocation.
– stderr
Okay this I have science but it would have some burden this modality? By what I’ve been reading the REST technology is by default statless ie Invocation. I use authentication in the access process because using Input I will have to redo authentication to each server request ?
– edmjunio
@edmjunio I believe in theory yes.
– stderr
I’ll test and report
– edmjunio