Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Is it possible to combine HAWHAW XML with PHP, ASP, or other server-sided scripting languages?

0
10 Posted

Is it possible to combine HAWHAW XML with PHP, ASP, or other server-sided scripting languages?

0

Yes, the platform independence is one major advantage of the HAWHAW XML approach. Even though there is no server-sided processing required to use HAWHAW XML, you can integrate every scripting language of your choice in your HAWHAW XML file. One principle of server-sided processing is, that the receiving browser only sees the result of the processing and not the script itself. Considering this, it becomes clear that a HAWHAW proxy has not to deal with your script code at all. A HAWHAW proxy awaits HAWHAW XML markup. It is in your responsibility whether you store this HAWHAW XML output in a static file or whether you create this output dynamically. The demo section of the HAWHAW homepage shows some examples how PHP scripts can be integrated in a HAWHAW XML file. The extension of your HAWHAW XML files is of no importance. The extension .xml is recommended for static files. If you integrate PHP code in your file, it has advantages to choose an .php extension, for ASP just name it .asp.

0

Yes, the platform independence is one major advantage of the HAWHAW XML approach. Even though there is no server-sided processing required to use HAWHAW XML, you can integrate every scripting language of your choice in your HAWHAW XML file. One principle of server-sided processing is, that the receiving browser only sees the result of the processing and not the script itself. Considering this, it becomes clear that a HAWHAW proxy has not to deal with your script code at all. A HAWHAW proxy awaits HAWHAW XML markup. It is in your responsibility whether you store this HAWHAW XML output in a static file or whether you create this output dynamically. The demo section of the HAWHAW homepage shows some examples how PHP scripts can be integrated in a HAWHAW XML file. The extension of your HAWHAW XML files is of no importance. The extension .xml is recommended for static files. If you integrate PHP code in your file, it has advantages to choose an .php extension, for ASP just name it .asp.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.