You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
eg, presuming your "normal" server-side php queries a mysql database and emits the result as json or html fragments or whatever, when the php itself is moved to-the-browser, how does the php now get the "dynamic" part of the data from the database, or from the server endpoint.?
becasue of http same-site security, the client-side php can't be arbitrarily reaching-acoss the network to anything other than the server-from-which it was delivered, and so it either needs to use long-polling or websockets to get that data, or php-wasm-cgi forwards the call up-stream to the server that delivered the http request in the first place...?
an example of this sort of dynamic constent is the entire reason php is on the "server" these days, so being unable to do it is massive thorn in the value it offers by putting it in-the-browser.
The text was updated successfully, but these errors were encountered:
@davidbuzz I just pushed out an update to Vrzno that enables url_fopen, so you should just be able to call $data = file_get_contents("https://YOUR_URL_HERE"); to pull data from a remote server. So long as CORS is enabled, it should work just like regular url_fopen. It runs a fetch() based GET request in the background.
eg, presuming your "normal" server-side php queries a mysql database and emits the result as json or html fragments or whatever, when the php itself is moved to-the-browser, how does the php now get the "dynamic" part of the data from the database, or from the server endpoint.?
becasue of http same-site security, the client-side php can't be arbitrarily reaching-acoss the network to anything other than the server-from-which it was delivered, and so it either needs to use long-polling or websockets to get that data, or php-wasm-cgi forwards the call up-stream to the server that delivered the http request in the first place...?
an example of this sort of dynamic constent is the entire reason php is on the "server" these days, so being unable to do it is massive thorn in the value it offers by putting it in-the-browser.
The text was updated successfully, but these errors were encountered: