Development · integration · reverse engineeringOstwald · Alsace · Remote projectscontact@dtouch.fr
WebSocket · states · interfaces

Real time & event architectures

The result of an action sometimes arrives well after its request. The Rey’actif ecosystem used WebSocket dispatchers for web applications and InDesign Server processing: an experience in the articulation between events, states and interfaces.

Separate the request from its result

A document generation or image processing may require a wait. The interface must be able to submit the application and then its evolution, without suggesting that the first acknowledgement of receipt is the final deliverable.

In Rey’actif, processing services and web applications were linked to WebSocket dispatchers. The integration work consisted of linking these components to steps understandable by users.

Connect InDesign Server events

Several processing managers controlled the InDesign Server environments. Checks for INDD changes and PDF status were other follow-up points in the chain.

The feedback must make it possible to distinguish a document to be processed, work in progress and available output. Events serve this common reading between the engine and the interface.

Maintain consistent state after interruption

A user can close his browser, lose a connection or return to a folder later. The design must provide for how to recover the status of the work and bring the information closer to the interface with that of the service.

We examine these scenarios during integration: reconnection, redisplay, processing completed between two views, and message received in an unexpected order. The service must remain intelligible in ordinary work situations.

Respect the user context

A notification must join the right session and the right business context. The Rey-Active environment included management of OAuth sessions and security codes sent by SMS.

The connection between access, events and files requires defining what each user can consult and trigger. The responsiveness of the interface remains linked to access control and data consistency.

Understanding the exchanges

Connect applications and keep exchange control.

Example of a path with deferred processing: the connector prepares the data, organizes their transfer and keeps the results of the exchanges for monitoring and recovery.

Connect applications and keep exchange control.Enlarge the diagram
  1. 01

    Sources

    API, files and databases

    Identifiers • formats
    Incoming data ↓
  2. 02

    Adaptation

    Business correspondence

    Fields • units • references
    Transformed data ↓
  3. 03

    Processing queue

    Organize requests

    Priority • planning
    Tasks ready ▼
  4. 04

    Execution

    Treating tasks

    Controls • matches
    Writing in the target ▼
  5. 05

    Destination

    Application or ERP

    Objects • management rules
    Returns and variances ▼
  6. 06

    Follow-up and resumption

    Control returns

    Journal • status • reminder
Connect applications and keep exchange control.Enlarge the diagram
Functional diagram · synthetic reading of flows and control points.
Identify

Keep the reference of the source and that of the target application.

Transform

Describe correspondences and distinguish direct calls from deferred processing.

Take over

Find the state and context of an exchange to be retired.

Your job deserves
the right tools.

A specific need, a software to evolve, a project to frame.

Exchange on your project

Complementary expertise, the same high standards.