[Info-vax] HTTP and HTML File Upload Basics

[Jan-Erik Söderholm]

Den 2020-10-21 kl. 21:22, skrev Arne Vajhøj:
> On 10/21/2020 11:27 AM, Jan-Erik Söderholm wrote:
>> Den 2020-10-21 kl. 16:41, skrev Arne Vajhøj:
>>> On 10/20/2020 8:18 PM, Dave Froble wrote:
>>>> At the core of a web server is a "listener" which can implement 
>>>> accepting incoming socket requests.
>>>>
>>>> The "payload" can then be some standard action, or, a "script" to 
>>>> execute can be part of the payload.
>>>>
>>>> Web servers usually are set up to perform some standard actions, and 
>>>> other actions will require a script for the desired action.  These 
>>>> scripts are what allows customization of a web server.  If very 
>>>> specific actions are required, that most likely will require a custom 
>>>> script.
>>>
>>> More common terms today would be "static content" and "dynamic content".
>>>
>>> Static content being HTML, CSS and JS.
>>>
>>> Dynamic content being PHP, ASP.NET, Jave EE, RoR, node.js, CGI scripts 
>>> etc..
>>
>> I would also count what is commonly called Ajax into the dynamic part.
> 
> Terminology can be difficult.
> 
> Seen from web server perspective a HTML5 bundle (HTML, CSS, JS) is
> static content, because the web server basically just considers
> them a bunch of bytes.
> 
> Seen from the user perspective it is dynamic content as it changes.
> 
>> I'm currently building a test mobile applications (POC) using
>> MIT App Inventor that first scans a product label (QR) and then
>> makes Ajax calls to our VMS system to fetch information for
>> display on the Android phone. Could be used on the factory floor
>> to quickly lookup the status of an item. A lot of fun and it
>> definitely makes “the old VAX” look better… 😊
> 
> What do you use for the web services?
> 
> Arne
> 

WASD as the web server frontend and PyRTE (Python Persistent Scripting)
with Python scripts as the backend. By using PyRTE there is no overhead
from the Python startup (which is usually 1-2 sec on our Alpha), the
scripts stays loaded and compiled within the PyRTE process and respons
times are done to 10s of ms. Well, you get the Python startup at first
access when the PyRTE process is created, it then lives for as long as
you have configured your idle time.

This works fine, we have built traditional web brower applications using
Javascript using the same backend.

https://wasd.vsm.com.au/wasd_root/src/python/READMORE.HTML