By Anthony Matarazzo
The implementation of a compiler system that is designed specifically for internet execution and distribution should be flexible enough to adjust itself for user response time in proportion to the available connection speed. It will be a goal of the render client to accurately measure the download stream time and keep this information up to date and readily available. This information could be communicated as part of the protocol via timestamp as statistics are gathered or by request means. Full blown applications, in machine code that is, are typically very large and therefore require time to download. I propose that using an overlay system during program startup in conjunction with the Very Large Instruction Set Model (VLISM) will facilitate the needed boost in speed that allows the user to quickly start working. The overlay functionality generation will be dynamically created by the Web Server and this will be a complex problem to engineer.
One solution is to have a predetermined list of bit rates and connect each bit rate to a series of overlay bank process. To facilitate the generalization that is needed, template oriented overlays can be used. They will expand or contract based on the specifics of the program requirements. The overlay banks would be switched dependant on the connection speed and therefore the only real noticeable artifact would be graphic image downloads and real-time audio playback quality. The audio mixing will be performed on the server of multiple channels so that a nice compact mp4 audio stream is available to the simple client.
Programs compiled using the system will allow the Web Server to query visual interface details ahead of time. If the program is document based, that will be a parameter of the query. This will be a service that runs under the web server category and will automatically be transparent to the users. Its job will be to store in a database all of the visual drawing language and startup overlay information. When execution of the program is requested by the client, it will be a fast SQL statement similar to “Select * from UserPrograms where pid=’WordPad.exe’ and Document=’ReadMe.doc’” call to the database management system.
The visual interface drawing command language will be an XML dataset that describes the coordinates, color, fill type and other rendering functions associated with the visual appearance of the interface. There are many languages already available like the Microsoft RC file format, and HPGL. Perhaps some would even consider HTML to be one such language. However, VLISM contains a consolidated combination of these languages that is specifically designed for internet transfer. These commands will be supported by the VLISM engine. The VLISM is robust so that when time or space can be saved the appropriate functions are available.
A new protocol utilizing UDP packets, much like HTTP, that communicates hardware platform details including client display type, resolution, color depth, and media features available will be needed by the host computer when preparing the VLISM stream information. This way many different client devices can connect to the same centrally stored user information but through a different version of the VLISM stream. One that is specific to the client device connected. One reason this is a great benefit, for example, is the resolutions available to Pocket PCs are completely different than laptops. So by creating a unique visual interface for each platform, the same code will execute on the server. This is a very important feature of program maintenance.
Abstracting the interface drawing from the client at this level allows greater client portability. No matter what device they are currently using be it the cell phone, mp3 player, portable next Gen laptop, or a pocket PC an operating interface will be there for the device. While the cell phone interface would be completely different than the full blown laptop version, the same connection point to the user’s data can be utilized. The features available to the user are now increased tenfold because the data interconnectivity between devices is an absolute. This interconnectivity would be purely a function of the operating system interface vendor to enable.
More planning is needed but I believe that a solution can be provided on the web server that encapsulates this functionality. Adoption by the industry of a standard Internet Assembly will also have to be accomplished (VLISM). So that, for example, when a user buys a new cell phone they simply encode their personal URL into the phone and all the software, interface and connection points are gathered by the web server on the back end.
The main goal of this system will be to facilitate the appearance and likeness of a desktop computing platform on a Minimalist platform or VLISM smart terminal. The VLISM smart terminal is a new internet computing platform currently in development.
The Many Devices of Connectivity