What is the best way to pass data between php files

Question

What is the best way to pass data between back-end and front-end, for example, send a form to the back-end, it executes an SQL script and returns an array of data that must be shown, what is the best way to pass this data to the front-end?

php form.:

<form action='./back.php'>
    <input type='text' name='teste'>
    <input type='submit' value='Enviar'>
</form>

back php:

$con = new mysqli("host", "user", "pass", "db");
$res = $con->query("SELECT * FROM tabela WHERE coluna = '$nome'");
$array = $res->fetch_all();

How to pass the $array for the front-end, I already imagined that sessions were not the best choice

Answer 1

The Controller’s function is actually just to handle HTTP calls to the application. An alternative for you would be to pass the business rules to a layer (directory) called Services. So you centralize these logics as services, and you don’t fill the controllers as much.

For example, you can create a Services folder and several subfolders inside.

- Services -- Orders -- Users

I also suggest you take a read on DDD, this can help you have a light:

https://www.devmedia.com.br/domain-driven-design-desenvolva-aplicacoes-com-qualidade/26116

I have something like that, but done in Laravel, but you may have an idea:

Already in this case, you may have a notion of how to organize Services:

Use and abuse the object orientation, gradually you will notice specific benefits and harm, but at first, I believe that these steps can already help.

Answer 2

Well, from what I understand, you’re using MVC (maybe changing the name of DAO). Following this premise, it is OK to create several controllers in the controllers folder. Actually, this is the idea.

Example of controller and its use:

Controler Client: Methods: Download, Create, Update

Call of methods, URL:

• http://localhost/Client/Get/5 - GET, where 5 is a client id, for example
• http://localhost/Client/Create - POST (JSON for example)
• http://localhost/Client/Update - POST (JSON for example)

With respect to passing data between controllers, this is actually not common. Normally, the view requests to the Controller, which based on information obtained by models, responses, etc. Sends the information somehow to the View.

Note, are layering

The way the view passes information to the controller, it can be GET, POST, PUT, etc.

The way the controller passes the information to the View depends on it. It can change in every language, platform, framework, etc. I recommend seeing MVC example in your language, in case PHP, correct?

Finally, here are some references. good luck!

https://tableless.com.br/entendendo-o-padrao-mvc-na-pratica/ https://www.devmedia.com.br/introducao-ao-padrao-mvc/29308 What is MVC(Model, View, Controller)?

Answer 3

Your architecture is a mess!

Let’s go in parts, before, understanding of HTTP:

1. the client makes a request
2. the server receives this request
3. the server processes this request
4. ... still processing...
5. the server responds with data
6. the client downloads the request
7. if it is a browser that is receiving HTML, the client renders

So your processing is free. And how do you do the processing? You said you want to "move from one PHP file to another PHP file", which doesn’t exactly make sense... PHP files weren’t meant to talk to each other the way you indicated. It even seems that you wanted a file to be executed, returned to the client and that then made a request right after to rescue the data obtained by the previous script. At least that’s how I understood your line.

Usually what is done is to create a collection of functions in a file more focused on the work of backend and, in the file more frontend, call these functions and display them correctly. To do this, you do not need to separate beautifully across all layers of MVC.

For example, this separation of data retrieval from the database and then display was made in that other question:

1. to original reply from @Sveen used the principle of separation of interface and bank
2. to my bitch (which is a variation of the @Sveen response, as I pointed out in the text) only gives an easier maintenance air; I turned a file inclusion usage into a function call

Because the only difference between the two answers was that I used a function, I’m going to focus on the original repsosta, @Sveen’s. The idea here was:

1. isolate in a component the display of a bank line
2. in the frontend, first make the database data independent basic statement
3. then into the core of frontend, obtain the various lines and, for each one, call the line display

Adapting to your case, it could be something like this:

back php:

<?php
function obter_linhas($nome) {
  $con = new mysqli("host", "user", "pass", "db");
  $res = $con->query("SELECT * FROM tabela WHERE coluna = '$nome'");
  return $res->fetch_all();
}
?>

front php.:

<?php include_onde 'back.php' ?>
<html>
  <body>
     <h1>Hello, world!</h1>
     <?php
       foreach (obter_linhas($_GET['nome'] as $linha) {
         echo "<li>Olha a primeira posição do array: ".$linha[0]."</li>";
       } 
     ?>
  </body>
</html>

Ready. We did the visualization of the data independently of the obtainment. In a way, we separated the "front" and the "back".

---

About the mess... the use apparent resembles very much something that would be an adaptive page. So, in that case, you wouldn’t need to submit the page for a full reload. An asynchronous reload of the minimally necessary part would be enough. For example, you could separate a <div> for your results and, when you redeem the values, write in this <div> (including discarding the previous values).

Using this type of thinking, you can have interfaces that display new information without needing a full page load:

To do this, you would need to send the data (the data itself, not the display of it; it is usually transferred in json or xml such data) from a endpoint PHP. On the client side, Javascript would take care of receiving this data, interpreting and then displaying it in the most appropriate way possible.

You will find more about this partial data request by searching about AJAX. By the way, this acronym means (or meant in the origins):

Tosynchronous JavaScript tond XML

In free translation:

Asynchronous Javascript and XML

Here, asynchronous means that the script will call a endpoint on the server and it will respond when possible, having no guarantee of when this occurs. Javascript is the programming language that makes the call and then treats the obtained response. And XML today is understood only as a data transfer, it doesn’t need to be the XML data transfer format.

Another use of AJAX you can see here, in Gitlab:

Here, when asking to display a tab, Gitlab starts by doing the asynchronous request, then putting the placeholder of the balls spinning so I think he’s working. When the request is finally completed, a Javascript intercepts the data and tries to display it to me in the best way possible.

Answer 4

You must separate into several controllers (remember that it is object orientation, unstructured). You define instances and they will have 1 controller, each.

Example: question instance, question controller will do all operations relating to questions on your system.

What you are looking for is called MVC (Model (your DAO), Vision, Controller). Use POST for insert and GET requests for read operations.

If you prefer to use a framework like Laravel, there emulate with some methods that HTTP does not support and better organizes requests like PUT for edits, DELETE for removals, GET for searches and POST for insertions.

Use Sessions for login information only!

Answer 5

Given what I see in the question , is a form for a Mysql, you can use GET to list there you will have your data passed by URL where you should make them friendly , you can use POST to add , PUT to edit and DELETE to delete , this FORM is very generic but I advise using an MVC to handle between your Front-End and Back-End , but if it is only for these pages , you will need to have the form sending the data to a page that will validate this data , include the database connection on this page and if the validation for Success moves the database, either viewing, adding , editing or deleting. Here we use PHP and Angular as an example:

// Incluindo biblioteca e configuração do banco de dados
require 'vendor/autoload.php';
require 'config/database.php';

// Retornando os dados no formato JSON
echo json_encode([
    'registros' => $registros,
    'paginacao' => [
        'registros_por_pagina' => $registrosPorPagina,
        'pagina_atual'         => $paginaAtual,
        'total_registros'      => $totalRegistros,
    ],
]);