How do I let a php application run on the client’s pc even if the server connection goes down?

Question

How do I let a php application run on the client’s pc even if the server connection goes down?

Asked 8 years, 8 months ago

Viewed 669 times

-4

Rectifying the previous question, I inform you that my idea is to let the customer navigate between application pages, perform records locally, and recover that data when the connection re-establishes.

1

"Offline PHP" is kind of weird. What you can do is run the PHP server on the client itself. It would be nice to be more specific in the question, because you already have 3 votes for closure as "too wide". Remember that you can [Dit] the question.

– Bacco

2016/02/28 at 21:29
Cara php is a language "servi side" it runs on the server the only way you leave the system running offline is using javascript and html that run on the "Client Side" platform however to save in database anyway you would need php on a local server

– Viniam

2016/02/28 at 22:22
You have to explain better, php offine You mean, let an application run only on a network without internet ? It became difficult to understand, is this talking about the unavailable database then make persistence elsewhere until there is availability to make the connection with the bank and from there record what would be in "buffer" or something of the kind... it became very difficult to understand saw

– SneepS NinjA

2016/02/29 at 11:45

2 answers

0

If you want to make your webapp available even if the server is off or the client without internet, you should use local Storage of HTML5. And of course, remember to only use the Storage location to save user data such as id, and username, never save password or personal data. Remember to use customer javascript to detect offline shipments ok?

Browser other questions tagged php mysql

You are not signed in. Login or sign up in order to post.

by epx • **8,191** points · Answer 1 · 2016-02-29T00:44:45+00:00

What you want, it’s not easy to get. I understand the motivation (keep the application available when Internet or server fail) but the application architecture would have to be considerably more complex to achieve this result. Imagine for example the situation: the system goes down, two users change the same registration while the system is out. How will these conflicting changes be reconciled? It is a sample of the kind of thing a distributed system has to deal with.