2004
DOI: 10.1007/s00779-004-0314-7
|View full text |Cite
|
Sign up to set email alerts
|

A Model–View–Controller extension for pervasive multi-client user interfaces

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
11
0

Year Published

2009
2009
2016
2016

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 20 publications
(11 citation statements)
references
References 5 publications
0
11
0
Order By: Relevance
“…A popular design pattern is the model-view-controller (MVC) pattern, which originated from SmallTalk: it is an architectural pattern that encourages pervasiveness and 'loose coupling' . The goal of pervasive application development is maximising the number of supported devices, while minimising code redundancy (Sauter, Vögler, Specht, & Flor, 2004). A typical problem of pervasive application development is to provide client-adapted user interfaces; for example, a homogenous graphical user interface between mobile and desktop screens.…”
Section: Design Patterns and Approachmentioning
confidence: 99%
“…A popular design pattern is the model-view-controller (MVC) pattern, which originated from SmallTalk: it is an architectural pattern that encourages pervasiveness and 'loose coupling' . The goal of pervasive application development is maximising the number of supported devices, while minimising code redundancy (Sauter, Vögler, Specht, & Flor, 2004). A typical problem of pervasive application development is to provide client-adapted user interfaces; for example, a homogenous graphical user interface between mobile and desktop screens.…”
Section: Design Patterns and Approachmentioning
confidence: 99%
“…The components are explained in the following text. [30]. Each component in the application logic layer in Figure 3 is implemented through appropriate MVC classes.…”
Section: Csmp/fon Architecturementioning
confidence: 99%
“…The problem of "stateful session handoff" is described in *4]. Some solutions have been proposed to help preserving and migrating browser sessions in multi-device environments [13,4], and some tools and languages have been made available to formalise this process [3,11]. But all session persistence techniques make use of a user ID or session ID (unique number) that needs to be typed manually or transmitted somehow from one platform to another.…”
Section: Migratory Interfaces and Multi-device Web Browsingmentioning
confidence: 99%
“…In some situations however, these solutions at client and proxy levels are not sufficient, for instance when the freshness of the session is essential (cf. section 4.3.2), and various server-side processing techniques can then be proposed [2,3,11].…”
Section: Partial Migrations and Platform-dependant User Interfacesmentioning
confidence: 99%