Read canvas image by HTTP: Difference between revisions

Jump to navigation Jump to search
Line 905: Line 905:
<canvasimage>/canvasimage</canvasimage>
<canvasimage>/canvasimage</canvasimage>
</syntaxhighlight >
</syntaxhighlight >
to the uri handler defined in file FG_ROOT/httpd-settings.xml and start fgfs with option "--httpd=5701" (the port number is free, but 5701 is used by the showcase HTML script). Enter the URL
to the uri handler defined in file FG_ROOT/httpd-settings.xml  
 
<syntaxhighlight lang="xml">
  <uri-handler>
                <screenshot>/screenshot</screenshot>
                <property>/props/</property>
                <json>/json/</json>
                <pkg>/pkg/</pkg>
                <flighthistory>/flighthistory/</flighthistory>
                <run>/run.cgi</run>
                <navdb>/navdb</navdb>
                <canvasimage>/canvasimage</canvasimage>
        </uri-handler>
 
</syntaxhighlight>
 
and start fgfs with option "--httpd=5701" (the port number is free, but 5701 is used by the showcase HTML script). Enter the URL
<syntaxhighlight>
<syntaxhighlight>
localhost:5701/canvasimage?type=png&canvasindex=0
localhost:5701/canvasimage?type=png&canvasindex=0
Line 912: Line 928:


The showcase script CanvasView.html shows the main instruments of Soitanens 737 with a refresh rate of 2 per second. This will not be enough for a smooth display and might be increased by reducing the timeoutinterval down from 500ms. But keep an eye on the overall performance of your running fgfs instance. Providing the images causes a significant system load.
The showcase script CanvasView.html shows the main instruments of Soitanens 737 with a refresh rate of 2 per second. This will not be enough for a smooth display and might be increased by reducing the timeoutinterval down from 500ms. But keep an eye on the overall performance of your running fgfs instance. Providing the images causes a significant system load.


== Related ==
== Related ==

Navigation menu