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

What is the meaning of cloudwall, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain for you in detail, people with this need can come to learn, I hope you can gain something.

Install the program in the database. The database is directly used as the back-end hosting program, and the document database manager is directly used as the cloud file storage program. No backend webapp, develop webapp in web

About a long time ago, I began to give up my efforts to unify distributed applications and local programs into the same appstack. There seems to be a natural gap between the two, such as the way applications are used. This artificial boundary is not used to cross. In the case of web, as a distributed architecture and distributed appstack architecture, it cannot be as flexible as native GUI programs or hardware accelerators. For example, web emphasizes that rendering everything on the broswer side leads to the need to use something like html5,webgl,js+css html to enhance it, so that it can be slightly like a local program. An example is WEBGAME implemented in WEB-this efficiency is completely different from that of game under local hardware acceleration, and the experience of WEBGAME is similar to that of traditional PC games, because hardware acceleration can never be achieved remotely and stream locally. Web uses http instead of native tcpip on the server side, resulting in the need for websocket to do things that native TCPIP can easily do like active push. Of course, there are many differences.

It's not WEB's fault. That's how WEB was defined in the first place: it's an ecology of advanced native tcpip programs. Its interface is PAGEUI, and PAGEUI is a rendering of the application layer. On the server side, WEB programs are mostly backend by things like LAMP,LNMP. This kind of program itself is actually an ordinary TCPIP program, not the basic component of a WEBOS, just like the task mechanism interface mechanism of native programs in the traditional OS implementation. That is to say, all WEBAPP have backend, that is, amp and other things in that lamp. They build a distributed appstack as a server and define an appmodel, so historically, things like WEBAPP+WEBOS are not pure.-WEBAPP is a point in the native interface that uses limited technology to build an entire stack ecology, so WEBOS is also an advanced OS on OS-- there is no WEBOS in itself.

Chromeos can't get away from the technical nature of X11 GDI plus a browser, which can't be compared to the really serious OS engineering. An APP management interface like Qunhui can be called webos. There are also parts like owncloud,standstorm: sandstorm has more xaas than oc.

As a cloud computing, web is responsible for defining the components of APPSTACK. The programs under cloud computing are nothing more than WEB programs, so the cloud has nothing of its own in the APP ecology except the virtualization layer. It is still the BS of advanced native distributed programs.

So, will there be a breakthrough in all this? One day, WEB will have something that doesn't rely on traditional BS architecture at all. Become like a truly independent, applied ecology made up of new things? And cloudwall may be another kind of "webapp": cloudwall does put forward a lot of new and refreshing things, although it is still oriented to WEBAPP, but some of it can generate new scrutiny as parts that are very different from traditional WEB, such as its nobackend design, and its slogan is also to the point: cloudwall,an Operating system for noBackend webapps. As it says, it even proposes a new prototype of webapp and webappstack,webos-which changes most of the traditional webapp.

The couchdb:the only backend as webos part of cloudwall

First of all, it uses apache couchdb, which is a documented database directly in line with WEB. If we call the APPSTACK we are going to talk about as the appstack of a certain WEBOS, then couchdb defines the only backend part of this appstack, which eliminates the need for lnmp as a backend: this is its unique feature that supports it and some component of lnmp these things are obviously different: this DB is documentary, and it nobackend.

Couchdb supports direct hosting app and running, called couchdb-hosted webapp, it adds something similar to the database manager is naturally an OC-like cloud storage program, supporting the development of various cluchdb plug-ins, this is webapp the whole cloudwall is such a couchdb manager.

CloudWall is an offline toy in a browser operating system for writing, storing, and sharing documents and CouchDB-hosted Web applications. CloudWall is installed by copying and can be run with only CouchDB and a modern HTML5-compatible browser. CloudWall can also be run as a set of files on static hosts.

All CloudWall components run in the browser tab, and no server or even internet connection is required after the system starts. Any local database can eventually be synchronized with an external CouchDB instance through http. A CouchDB can connect multiple users to provide shared workspaces, documents, and application sets.

In my "appstack series" and "app series" series of articles, I have been looking for cloud storage program selection, we have changed to mongdb,postgres, this program selection is actually WEBOS, we have put forward such attempts and ideas in these articles.

Let's take a look at a design of this kind of OS: is a stack necessary for an app? Enlarge its stack to be directly supported by WEBOS, and the OS technology behind this cloud program will become clear:

In fact, when considering that an app is equipped with an appstack, the limitation of relying on the native program appstack to define its own new appstack can never be avoided, because the mongdb,postgres here is always regarded as the dbbackend part of appstack, and webapp should not be obviously backend-free: like nativeapp stack, they should be integrated within a webos and solved in advance.

And couchdb is the whole thing that uses the database management system as OS to directly manage and store WEBAPP (of course, it can also manage static files directly like other document databases for cloud storage), if couchdb is like cloudwall as the entire webos, then the traditional webapp development is defined in this webos, the four appstack components of cloudwall are integrated in the webos concept called cloudwall os.

GDI: render HTML and receive user interaction

Application runtime: managing binding between data and UI controls

CloudWall: preparing, running, and closing applications, managing application switching

Storage: stores applications and documents, optionally synchronizing with external CouchDB instances

And this kind of development, has made webapp development become like local (do not need to deal with the part of appstack only need to focus on things within app), we have always hoped to achieve the effect: webapp like local file storage as the back-end is in line with the habit of local applications, this goal has also been achieved.

Inapp editor in cloudwall: language and Development Section

In all the efforts of "bcxszy series", I want to get such a program and development approach: without changing the general aspect of native programs and webapp, making WEB programs as simple as native programs, so that we can share the concept of native programs / webapp development. In terms of obfuscation appstack, which is mentioned in couchdb in cloudwall, has been resolved. What I'm going to talk about here is the part related to language development:

It can be said that in all the efforts of "bcxszy series", I also want to promote such a program and development method: source code is a file, packing and walking everywhere, and direct per app an ide development, which is very convenient for both practical and development, self-learning programming.

Fortunately, WEBAPP src text-based, supporting lightweight take-away inplace editor is its natural advantage of all WEB programs, and although there are many differences between WEB programs and local programs at the beginning, things like WEB standardization, HTML standardization, JS language standardization and so on, are actually taking a joint effort direction to make the WEB ecology close to the local ecology. for example, one of the efforts of JS is nativejs:reactos.

In fact, the other side of the tight combination of couchdb and web is that js,js is an enhancer that can really bring the integration of naitveapp and webapp, which makes cloudwall support extremely convenient inappeditor, so the development of plug-ins supported by cloudwall is the development of webapp under cloudwall webos, which supports direct storage and editing of files in the process of app development with couchdb.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

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.