Subscribe for automatic updates: RSS icon RSS

Login icon Sign in for full access | Help icon Help
Advanced search

Pages: 1 ... 8 9 [10]
 91 
 on: September 25, 2019, 12:52:33 pm 
Started by Gary C. - Last post by Gary C.
Hi

Thanks for the reply. It may by my lack of understanding but is the USER_AGENT element still relevant when using GDC as the front end?

The manual states that USER_AGENT is a child of the TIMEOUT element which itself is a child of the UA_OUTPUT element. I only use UA_OUTPUT for our GBC applications.

Gary

 92 
 on: September 25, 2019, 10:35:02 am 
Started by Gary C. - Last post by Frank G.
Hi,

  The auto logout is not fired immediately after 30s of inactivity, it depends also on the USER_AGENT timeout that is set to 300s by default. Because as there is no activity, the user-agent is only notified of the logout at next request it fires, and this is at USER_AGENT timeout.

Can you try to reduce the USER_AGENT timeout to 60s, you should get logged out after one minute.

Frank

 93 
 on: September 24, 2019, 02:32:07 pm 
Started by Gary C. - Last post by Gary C.
Hi

Reading an earlier post made me aware of the auto logout feature which I think would be of benefit to me to ensure users are logged out each evening - they have a habit of just leaving their screen and heading for home at the end of the day.

However, I cannot seem to get it to work. We use GDC and GAS to launch an MDI based menu application from which all child applications are launched in docked tabs.

Here is the extract from the menu applications XCF file.

Code
  1.  
  2. <APPLICATION Parent="defaultwa">
  3.        <RESOURCE Id="res.teqdir" Source="INTERNAL">/opt3/teq</RESOURCE>
  4.        <RESOURCE Id="res.teqdir.bin" Source="INTERNAL">$(res.teqdir)/bin</RESOURCE>
  5.        <EXECUTION>
  6.  
  7.            <PATH>$(res.teqdir.bin)</PATH>
  8.            <MODULE>teqstart.42r</MODULE>
  9.  
  10.         </EXECUTION>
  11.         <AUTO_LOGOUT>
  12.             <TIMEOUT>30</TIMEOUT>
  13.         </AUTO_LOGOUT>
  14.  
  15. </APPLICATION>
  16.  
  17.  

I was hoping that after 30 seconds of inactivity some form of popup would appear but nothing does. Can anyone point out the error of my ways?

Many thanks

Gary

 94 
 on: September 19, 2019, 11:41:22 pm 
Started by Efisio S. - Last post by Reuben B.
If I understand the question correctly, it is for cases for long running reports or processes that may take upwards of 5,15,60 etc minutes to run.  This program might have some UI in the form of a  process indicator e.g. Processing 1 of 1000 records, Processing 2 of 1000 records etc and/or it might have an interrupt button so that the user can stop it.  With the typical GDC over SSH setup, you could be assured that as long as the SSH connection stayed up between the GDC on your PC, and the fglrun process on your back up server, then this report/process would continue to be run.  The same is true with GBC/GAS/HTTP, that is the report/process would continue to run due to the keep-alives occurring behind the scenes , you are not forced to "implement a kind of job system" by moving from GDC/SSH to GBC/GAS/HTTP.

However you might want to consider the following ...

1. If you decide to enable AUTO_LOGOUT, what will happen to these long running programs with UI that typically take longer than the AUTO_LOGOUT period?  ...

2. How difficult is it for a user to close the GDC and what will be their typical response to the dialog that appears, versus the equivalent web behaviour which is closing a browser tab and their typical response to the dialog that appears?    I would argue that a typical user is unlikely to attempt to kill gdc.exe, and is likely to respect the dialog that appears if they attempt to do so, whereas in a web environment, closing a browser tab and ignoring the warning dialog, is something they are more likely to do, and it is for that reason you might want to consider to "implement a kind of job system which executes these operations in the background"

Reuben



 95 
 on: September 19, 2019, 05:51:50 pm 
Started by Efisio S. - Last post by Efisio S.
Hi Frank,

The thing that most worries me is to lose the session during a long running operation.
Is it suggested to keep an operation running for hours in a GBC window or not?
What I don't want for sure is to be logged out while waiting.
I'm asking this because on the web generally it's not recommended to make users wait for a long running operation end in a web page.

Thanks

 96 
 on: September 19, 2019, 05:29:27 pm 
Started by Efisio S. - Last post by Frank G.
Hi,

 By default, if you start a GBC application through the GAS, your application will star alive until you click the close button in your app. This is the expected behavior.
If you want you application to close after some inactivity time, there is an AUTO_LOGOUT feature to be set in the xcf of your application to end it after a given time of inactivity.

What do you want to achieve actually ?

Frank

 97 
 on: September 19, 2019, 05:17:48 pm 
Started by Efisio S. - Last post by Efisio S.
Hi,

We are migrating an application from GDC over SSH connection to GBC through GAS HTTP connection.
Since HTTP protocol is stateless, i'm wondering if long running operations we used to launch and wait with the GDC over SSH can be run in interactive mode, waiting their end on a browser page or if we should implement a kind of job system which executes these operations in background.
I noticed that when an FGL application is busy and doesn't update the ui for a certain amount of time, GBC starts some web requests to the GAS which take 60 seconds to return a response by default (because of the REQUEST_RESULT parameter I suppose)
What do fourjs gas/gbc devs recommend me? And also, what are the experiences from fourjs customers devs in this regard?

Thanks

 98 
 on: September 18, 2019, 10:29:05 am 
Started by Efisio S. - Last post by Efisio S.
EDIT: I uploaded the wrong customization archive. Here is the working one. Sorry

 99 
 on: September 18, 2019, 10:13:08 am 
Started by Efisio S. - Last post by Efisio S.
Hi Susobh,

Thank you for the help.
I made some changes, like extending the chrome bar widget and removing the hidden header bar, which event listeners had been replaced by the same listeners in the container javascript code.
The result is good, so I can proudly attach a screenshot to show it to you.
One thing that I wasn't able to handle is the badge counter when there is specified an application icon from the fgl program, which overrides the hamburger menu icon, therefore in the extension of the chrome bar widget I added a few lines for hiding the custom icon and keep the stock gbc icon.

Bye!

 100 
 on: September 18, 2019, 05:46:41 am 
Started by Efisio S. - Last post by Susobh S.
Hi,

Please take note, that you may not want to make the ChromeBarWidget changes directly.
In Case if you have extended the ChromeBarWidget, you can always paste the changes in your extended ChromeBarWidget.

For my sample to you, i have directly modified the ChromeBarWidget Javascript and Template directly

Thanks And Regards
Susobh Sugathan

Pages: 1 ... 8 9 [10]
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines