Shulou(Shulou.com)06/01 Report--

How to use the idea of developing local tcpip programs to develop webapp, I believe that many inexperienced people do not know what to do about it. Therefore, this paper summarizes the causes and solutions of the problems. Through this article, I hope you can solve this problem.

It is undeniable that webapp is already one of the mainstream appmodel juxtaposed with desktop and mobile app, but web is a typical Appstack as os,webapp, which is a bUnip hole in native server apps, and then the whole world is developed in this hole (like mobile APP, such as Android). For example, the appstack under it falls into the category of native/desktop, and the person in charge of gui is nginx,db mysql,etc (representing webappstack is server app). The client is just "client side html,js resources". If it is separated from the server, it has no meaning of its own existence. Not a stand-alone available app)..

Vs nativeapp and nativedev, which never has its own os, or any standard host definition. Compared with native app, it is not a kind of "app" with a special OS for it to host and run. If you say that the host of webapp is lamp, it is obvious that the l in lnmp does not belong to web, nor is it applicationserver?beanserver?, it is the component server of the language, in other words, only things like nginx,mysql belong to web-- that is to say, technically, through the combination of ln+np, you can produce a web program. This is similar to mobile development, they are both app,--- under the dual hosting of linux and a virtual machine language, web development and mobile development are at the beyond native level, and that's all.

Design and defects of web

In development, the web app of dynamic programs is integrated by the front and back end of monolith, called page app, and programmers complete all program development at the back end. The framework logic of Webapp is nothing but routing,template,orm,route,mvc. What represents an appmodel is nothing more than its stack framework logic. Because it takes into account that the browser is an integrated app of the server and the client. There is no interaction and reuse between web programs, no api mechanism, no web components, web as service (of course, these later.) Only at the language source level

Applications, and back-end operations and maintenance, are also integrated in web. Users do everything on a web interface, such as cms back-end management. Users and content are also integrated remotely. No offline, only online. That is to say, the program depends on the back end, the content depends on users, it is distributed online, and there is no offline distribution, and it is all monolitch (and there is no second choice for specific options such as http,js, making webapp fixed).

None of the above is a problem. It's not web's problem. Just like when Web first came out, it was actually distributed static documents, but then someone used it to force webapp (and the implementation of distributed application development is very broken in industry, there is no real distributed OS, there is no distributed appserver, see "plan9 a real distributed OS")-historically, long links, webgl,streaming content, these It has always been an effort to overcome and diversify web monolitch page appmodel from all dimensions.

However, it can only be distributed on the wire, not offline. The disadvantage of web is obvious. There is a practical need to put web online, that is, there is a demand that is different from the reality of real web applications, for example, is there a distributed webapp that cooperates online and offline? Do those that can be handled locally let it jump out of browser without having to manage it remotely, such as the back end? Just like git's distributed approach,-We've been talking about this kind of thinking before, such as using static website ideas to develop webapp, and using tcpip to develop BUnix s.

New webapp

Such a scheme exists, and there are projects like wordpress headless cms on the Internet, and the result of such efforts is to re-place web at the specification level and redesign webapp. It only needs to be a http protocol, and it does not have to be an app,web. It only needs to be a gui, not all of full appstack. This separates the online and offline. Both online and offline are developed separately, both of which are linked through api.

There are many benefits of re-separation, the most obvious of which is the development:

1) the server of Web can be transformed into an as service service as a headless backend. There are api mechanisms and reuse. Customer service is developed separately, and developed in the way of Cramp / s and similar to nativedev. Customer service is no longer rigidly adhered to each other's technical specifications and language technology selection.

2) simplify server-side development and selection, display logic separation, server-side web framework no longer use things like mvc and other logic to deal with client-side routing, and Lnmp no longer need php. It can be implemented in any language on the server side. There can also be a multi-choice selection structure such as gitstack. Or just other non-lnmp xxxstack that uses http, so the back end of webapp can be anything.

3) the client development is offline, and webapp is no longer regarded as an appmodel of monolith, but is similar to CUnip s web. You can use any language to implement html as an asserts in the editor, not just a browser. , which can be another independent client app

4) change to "thin server development" and "strong client development", such as Wordpress, plug-ins can be done on the client side instead of open source. Or vice versa, complex online interactive sites are fine (but there are other ways to solve them, aren't there? For example, make the dynamic part into a headless "chat", headless "comment", headless "xxx"?).

In application:

1) cms can be developed to be managed locally by headless cms, with a truly independent client app and fully Turn into functional in-browser application.

2) if it is a display site such as cms, the remote web program only needs to be a storage space. Such as Aliyun OSS. In this way, a static space can solve the problem of cms hosting and is more professional.

There's more.

In fact, the above points have the same meaning as "treating b webapp as s webapp as c Unix s webapp in nativedev manner".

After reading the above, have you mastered how to develop webapp with the idea of developing local tcpip programs? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.