The cache component

The cache component


Many of the features of this platform is enabled by the local cache component. It is the component that handles most of the communication with the server. It does currently not handle all communications as it lacks the features for specific requests.

When data is requested, the component first search it's local store before contacting the server. Depending on the nature of the request, it may decide that server contact is not necessary and returns data from the local store only. If some data is found locally it may ask the server for more before responding to the request. This method keeps server load as low as possible while also making the system respond quicker to requests. When a record is updated on the server a short message is dispatched to all it's clients, if a client has this record in it's store it will be flagged as outdated, though it will only be refreshed when requested. This way the cache component knows which data is up to date.

When the cache object spots a 401 (unauthorized) response, it automatically flush all data to reduce the chance that it falls into unauthorized hands. This response is received if your session in the server times out due to inactivity.

The cache component also has some functionality around realtime updates, though this is a bit outdated currently. If a data view is active and display a record that is flagged as updated by the server, then the cache component attempts to update the data view.

Kommentarer

Skicka en kommentar

Populära inlägg i den här bloggen

The form component

Bild
The form component Forms are one of two main components of the tool. It allows the entry of any type of data. Forms are created in a built-in visual designer, my intention was to make it WYSIWYG but i'm not quite there yet. HTML is a bit difficult to get right. Below is a screenshot of the editor with the 'New incident' form loaded. In the editor you can add most standard HTML elements such as text boxes, list boxes and buttons. You can also add components that are built for this tool only, such as panels, data views and tree views. This is where the tools shines: You can add complex components not native to HTML with little or no code requirements. Many methods are pre-built, for example the form submit. You can add this method to a button click by simply setting it's submit property to true. The same thing can be accomplished by code if desired. There are scripting capabilities for many types of events.  Below is a screenshot of the form in the editor when executed on...
Läs mer

The data grid component

Bild
The data grid component The other day i started working on a grid component for the forms. I have thought long and hard about how to solve some of the problems of unforeseen data. I have added array capabilities for fields if that is required, but it is not a very flexible solution. The filtering assistant of the data view is an example of this functionality. Then i realized that a grid component could solve many of the issues so i started working on one. The image below illustrates a grid component in the visual designer, very early in the development: Like everything else the idea is the possibility to create a fully working grid without writing any code. There will be limitations in functionality, but it is doable. The image below shows the grid component in the visual designer after some more development Now we are starting to get somewhere, but a fully fletched grid needs a lot of functionality that will take time to develop. One such functionality is to link the system's pick...
Läs mer