When developers start using our newer products I often see them jumping in the deep end, trying to run before they can walk, biting off more they can chew etc. and their first experiences are not as positive as they can be. Over time I am going to do a series of articles entitled “Starting …” where I will explain what I think are the key concepts and points you should understand with our products and try to make your initial experience a positive one. Today I will look at Genero Application Server (or GAS).
Most of you will come from a background of using GDC with Direct Connection, you will first encounter Genero Application Server (known as GAS) when you want to do one or more of ...
a) Use the Genero Desktop Client (GDC) via HTTP
b) Use Genero Browser Client (GBC)
c) Provide Web Services (GAS is not needed to consume Web Services)
d) Use runOnServer with Genero Mobile
You can think of GAS as having to do two things ...
1) Start your Genero applications (fglrun process)
2) Manage the communication between a Web Server and the fglrun process
So when a user types a URL into a browser, or clicks on a link to a Genero application, or another program makes a web service call to consume your web service, the GAS is responsible for starting the appropriate program (fglrun) if needed, and managing the communication backwards and forwards between the fglrun process and the ...
a) GDC in the case of a program running GDC via HTTP
b) browser in the case of a program running using the Genero Browser Client
c) web service consumer in the case of a Web Service,
d) Genero Mobile container app in the case of runOnServer
Read more at
https://4js.com/ask-reuben/ig-93/
Sign in for full access
Help
