Glossary

Client Helpers (Basic Features)

Updated frontend helpers to work with this latest versions using Angular and Kendo UI Components for Angular.

Web Server (Basic Features)

Support for ASP.Net Core applications
Data-Query: Mechanism to Query for specific data to the WebServer using ASP.Net Core WebAPI.

C# Language support

C# Syntax 7.3 or previous version is fully supported

Application State

Memory Management Automatic memory management on web environments
Static Members Support for static elements on web environments
Basic Collections Support Support for List and Dictionary and data queries for frontend support.
Model Synchronization Moving data between the backend and the frontend, introduction to Mappers and Data Transfer Objects(DTO).
Serialization: Persist the state of object between requests allows the system to unload unneeded objects from memory.
Error Handling: WebMAP Core Services offers a mechanism to report and handle exceptions

Web Server:

Session Management: Support for session management out the box using the provided mechanism of ASP.Net Core.
Flexible Communication Protocol: Flexible protocol that allows WebMAP5 to synchronize state and execute custom actions.

User Interaction

Desktop Compatibility Platforms: This layer allows WebMAP5 to support different technologies, for example WinForms or Power Builder. These Desktop Compatibility Platforms consist of all the Models, Event Handler Mechanism, Mappers, DTOs, Error Handling, Server Commands and Observable Wrappers needed for each technology. Each DCP is pluggable so different desktop layers can be supported by the same WebMAP Core Services layer. At the moment just the Windows Forms platform is supported, and the Power Build being under construction.
Modal Dialog: The WebMAP Core Services provide a mechanism that allows for the server to stop the execution of a request and wait for a response from the user and then continue with the execution of the previous request.

Debugging

The debugging experience is improved by hiding WebMAP Core Services tasks from the user application code, and leaving the original Bussiness logic unmodified.
Logging: An extensible logging mechanism is provided by WebMAP. This eases the debugging process, allowing to easily pinpoint a problem.

Documentation

This version provides better user and developer documentation which is available online and continuously updated.

PreviousWeaving on WebMAP NextFAQ

Last updated 4 years ago

Was this helpful?

Application State

Memory Management Automatic memory management on web environments

Static Members Support for static elements on web environments

Basic Collections Support Support for List and Dictionary and data queries for frontend support.

Model Synchronization Moving data between the backend and the frontend, introduction to Mappers and Data Transfer Objects(DTO).

Serialization: Persist the state of object between requests allows the system to unload unneeded objects from memory.

Error Handling: WebMAP Core Services offers a mechanism to report and handle exceptions

User Interaction

Desktop Compatibility Platforms: This layer allows WebMAP5 to support different technologies, for example WinForms or Power Builder. These Desktop Compatibility Platforms consist of all the Models, Event Handler Mechanism, Mappers, DTOs, Error Handling, Server Commands and Observable Wrappers needed for each technology. Each DCP is pluggable so different desktop layers can be supported by the same WebMAP Core Services layer. At the moment just the Windows Forms platform is supported, and the Power Build being under construction.

Modal Dialog: The WebMAP Core Services provide a mechanism that allows for the server to stop the execution of a request and wait for a response from the user and then continue with the execution of the previous request.