H3S1: Collapsing multiple functions:
From mysql-lib: select single grid and fetch password both select from a tb single grid where a single , so I can combine them, and take more arguments<Turing>
function select_single_grid($post_author_username, $post_ID, $column) {
$sql = "SELECT $column FROM dash_{$post_author_username}_posts WHERE post_ID=$post_ID";
global $conn;
$result = $conn->query($sql);
$row = $result->fetch_assoc();
return $row["$column"];
} function fetch_password($username) {
$sql = "SELECT password FROM users_tb WHERE username='$username'";
global $conn;
$result = $conn->query($sql);
$row = $result->fetch_assoc();
return $row['password'];
}H4S1: Combined function:
Hu: A tertiary function will focus on the core idea of selecting from a single | grid in a table, any table, and returning $row[‘column’] that corresponds to that grid. Most likely, the function will need to have 1 required parameter, and some optional parameters, depending on the use case; both use cases need to be supported.
H4S2: How these functions are called:
Hu: Keeping an eye on # how these functions are called can help us determine their structure:
H3S2: Contribution log:
H4S1: URL handling is inconsistent for local vs web traffic: security@apache.org 12/11/22
Hi Apache foundation,
I'm an Apache user in the WAMP case and I recently configured 2 firewall levels, and httpd-vhosts.conf to open up several virtual hosts to web traffic. Previously, I have been using micro-services from local only, and all of my script-based URL specs are from this angle.
See here for more details:
https://www.wordpress.materialinchess.com/2022/10/30/h2s76-finagling-tcp-ip-architecture-to-enable-true-peer-to-peer-domain-less-information-ex/
H2S114: Apache.HTTP-serv,lit.rev:
When the web traffic was opened up, I ran into several issues with my relative path specs; the handling is inconsistent, and directs users out of the virtual host:
H2S41: Web-URL code design, data-storage:
^ see H3S7
Obviously, I cannot use absolute path, because public visitors need the IP spec as a prefix: http://71.126.6.14/ also obviously, I cannot send local users back out, and in again<Torogi, a-r>:
Therefore, I may have to build a conditional handler, that recognizes on some level of WAMP, and potentially, redundantly already with the action of Apache, possibly in PHP, using $_SESSION https://www.php.net/manual/en/reserved.variables.session.php to store the source address, and use this to toggle the URL handling manually, but this defeats a significant part of the purpose of Apache, whereas for you, it's maybe a 1 line code change, and this is already a security vulnerability.
Let me know how this might be able to fit into the pipeline.
Thanks,
Yakun
References:
Torogi: https://www.youtube.com/watch?v=gmXwGZK2uZoH4S2: Request for support functionality of socket programming: contact@thephp.foundation: 12/11/22:
Hi,
Doing low level socket programming will be the primary driver of internet growth over the next 10 years, as the web transitions from an HTTPS only paradigm to also include real-time protocols; this will dramatically increase user engagement, since user count is saturated #
PHP is currently the most well-supported for lang for socket programming, contrary to popular belief. However, there is a small handful of features that are missing, that prevent a true low time, and efficient implementation.
I've documented below:
https://www.wordpress.materialinchess.com/2022/11/14/h2s119-granular-control-of-interpreter-waterfall-between-https/
H2S112: Socket programming in C:
H2S113: A +1 o.o-m granular testing paradigm for protocol-dev |=full research:
See the rest of my blog here, for auxiliary details.
Presently, Apache-HTTP's persistent listener is the only reason that PHP is a web-lang, and not a basic calculator. The ability to set up persistent listeners natively in PHP, including for real-time protocols, would multiply the applicability of the lang.
Thanks,
Yakun