Springfield and the Multiscreen Toolkit

Our product are based on the Springfield and the Multiscreen Toolkit, which allows a wide range interaction between phones and the main screens. An important aspect of the Multiscreen Toolkit is that it creates HTML5 apps which means all interaction will be browser based, your consumers will not forced to download and install an App Store application. An important aspect of Springfield is that it consists of different independent services. Each service is contributing to a specific function or activity.

Springfield and the Multiscreen Toolkit are published on Github as an Open Source products, allowing external developers to use the product in their own way. External parties can also use running Springfield services (on the Noterik cluster) within their own systems using our APIs. In this setup we can provide help for tailoring the components to particular needs.

Overview of the different services inside Springfield Framework

Smithers is a server-side Java application which runs within a J2EE application server using a web form file system. This is the heart of the WebTV system in the sense that everything that is made will be saved in Smithers to xml (fsxml format). Smithers works via the REST principle and is thus easy to communicate with Springfield.
Bart is a simple proxy service. The Springfield house is fairly open (so­-called soft core design, similar to most operating systems) and the services are not directly accessible from outside. Communication is done via a gateway where all requests from outside is evaluated and if it is accepted, will be transferred to the Smithers service. Bart is a fairly simple system and runs as a service within a J2EE Java application server.
Barney provides authentication for a Springfield cluster. This is by purpose a separate REST service so that in future it is easy to connect to external access systems such as LDAP, Aselect or other systems without having to adapt the code of Smithers.
Homer and Marge form the basis of the system administration of the Springfield cluster. This means that Homer keeps track of where the services and servers are located and is the source of communication for all internal and external applications. Marge is a plugin (Java or command line) which should be implemented by a application / service as a means of communication with Homer. Marge provides status information, ensures that the services subscribe / unsubscribe and is open to questions from Homer. Homer is a J2EE application, Marge is deliberately a simple Java application that can run stand alone or simply included in software from third parties.
Nelson is responsible for making screenshots of the videos in Springfield. Basically it can make screenshots on request but the standard way in Springfield is to make a screenshot of every second of each video. These screenshots are used during the scrubbing of the video, previews, editing and pre-loaders. Nelson is a J2EE application written in Java.
Flanders is a data mining service. At the request of Smithers, Flanders examines a resource and complements them with meta information. It should think of lengths, formats, codecs and other meta information to be hidden in video, images and audio files. Flanders is a J2EE service and is written in java.
Lisa is responsible for complex indexing and search, and sometimes we call her our problem child ;­) Springfield is an XML based filesystem for which makes searching through these 'documents' difficult. Lisa is based on what is commonly used and / or appropriate indexes so that it can be easily searched in resources. Lisa gives answer in the form of a list of found resources, and because everything is based REST is in the form of URLs so that the requesting entity simply can deal with. Lisa is a J2EE application written in Java and uses Yahoo's Lucene to create some indexes.
Apu is a client side Java application (web­start) which allows the client encoding large video files and upload. This is because modern video cameras (cameras and more pictures) files to deliver such high quality and thus instantly upload size that is unattainable. Apu makes it possible for people to select video files on their computer and these are then converted to the same size as requested in Springfield and uploaded. Apu is a residual and applet using web­start application that asset is put to installation by the user so people do not need.
Krusty is a video playback application which we originally wrote in Flash 9 (ActionScript 3.0) but some tactical influence of Apple forced us to build an HTML5 version. Krusty is highly integrated with the Springfield cluster so it can play complex video playlists (presentations) for the user user. Krusty is highly programmable from the file system (Smithers) per domain, user, collection or even depending on the presentation it plays.
The goal of Eddie and Lou is to provide developers with tools to easily develop applications with multiple screens. Eddie plays the part of the front-end service utilizing HTML5 and Javascript technologies, while Lou is the Java powered back-end service. Together they work to display information across multiple screens and provide users with a seamless experience between different devices. By breaking down compete applications into smaller ‘components’ we can push them individually to screens (e.g. authentication boxes, video controllers, subtitles etc.). Combined with the flexible messaging system, the possibilities are endless.
микрозайм онлайн круглосуточно займы онлайн микрозайм в интернете на карту