reTHINK-project core-framework issues

reTHINK-project / core-framework

The main goal of WP3 is to provide the reTHINK core framework comprised by the runtime environment where Hyperties are executed and the messaging nodes used to support messages exchange between Hyperties.

Apache License 2.0

1 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Runtime UA 0.1 Implementation

#56 pchainho closed 9 years ago
0
Domain Login

#55 KCorre closed 8 years ago
1
Runtime DynamicView Basics

#54 aoncorici closed 8 years ago
1
Browser Runtime implementation

#53 avallee-apizee closed 9 years ago
7
H2H Intradomain Communication

#52 pchainho closed 9 years ago
6
M2M Connector in the Runtime

#51 pchainho closed 8 years ago
1
LHCB Description

#50 emmelmann-fokus closed 9 years ago
5
Crafting the Service Framework

#49 acheambe closed 9 years ago
6
Hyperty Core Runtime functionalities implemented with Service Workers

#48 pchainho closed 9 years ago
1
Hyperties Origin

#47 KCorre closed 9 years ago
6
Adoption of TypeScript over Javascript

#46 shumy closed 9 years ago
14
Runtime PEP and PDP

#45 pchainho closed 9 years ago
1
Service Framework MUST be Message Node agnostic.

#44 pchainho opened 9 years ago
0
The Service Framework MUST avoid any JavaScript conflicts

#43 FredLuart opened 9 years ago
3
Service Framework MUST be Modular in nature

#42 acheambe opened 9 years ago
0
Runtime Architecture

#41 pchainho closed 9 years ago
7
The sota folder should be restructured and cleaned up

#40 sdruesedow closed 9 years ago
2
The Service Framework MUST be open source

#39 acheambe opened 9 years ago
0
Service Framework should be device agnostic

#38 pchainho opened 9 years ago
0
Service Framework MUST be light weight and fast

#37 acheambe opened 9 years ago
0
Service Framework SHOULD support Model-View-Controller design pattern

#36 acheambe opened 9 years ago
2
Messaging Node should be resilient

#35 acheambe opened 9 years ago
7
The Messaging Node MUST offer DoS and DDoS Protection

#34 acheambe opened 9 years ago
0
QoS component should assure collaboration between network and application layer actors

#33 EwaJan opened 9 years ago
1
QoS component should provide a single contact point for troubleshooting issues

#32 EwaJan opened 9 years ago
1
QoS component should enable isolating and valorising performance improvements

#31 EwaJan opened 9 years ago
0
QoS component should leverage IP paths diversity

#30 EwaJan opened 9 years ago
0
QoS component should impact different network types and segments

#29 EwaJan opened 9 years ago
0
QoS component should be compatible with evolution of different standards and terminals

#28 EwaJan opened 9 years ago
0
QoS component should be compatible with deployed network technologies

#27 EwaJan opened 9 years ago
0
QoS component should be compatible with application layer technologies e.g. WebRTC

#26 EwaJan opened 9 years ago
0
QoS component should exploit partially SLA and partially best-effort network segments

#25 EwaJan opened 9 years ago
0
QoS component should take into account participating and non-participating actors

#24 EwaJan opened 9 years ago
0
QoS component should have global reach

#23 EwaJan opened 9 years ago
0
Create Vert.x

#22 acheambe closed 9 years ago
0
Messaging Node should support Protocol on-the-fly

#21 pchainho opened 9 years ago
0
Messaging Node should support different Encrypted Messaging Transport Protocols

#20 pchainho opened 9 years ago
0
Message Caching

#19 pchainho closed 9 years ago
1
Messaging Node should support logging of routed messages

#18 pchainho opened 9 years ago
0
Message must support delivery reliability

#17 pchainho opened 9 years ago
0
Messaging Node must support worldwide scale deployments

#16 pchainho opened 9 years ago
0
Messaging Node should be tolerant to unstable connections

#15 pchainho opened 9 years ago
18
Events must be fired when clients connect and disconnect from the Messaging Node

#14 pchainho opened 9 years ago
0
Messaging Node must support very low message delivery latency

#13 pchainho opened 9 years ago
0
Messaging Node must be deployable in the most used Virtual Machines

#12 pchainho closed 9 years ago
2
Messaging Node should require minimal computing resources

#11 pchainho opened 9 years ago
0
Messaging Node must support external authentication and Authorisation

#10 pchainho opened 9 years ago
0
Messaging Node must support multiple message oriented communication patterns

#9 pchainho opened 9 years ago
1
The effort to introduce new capabilities in the runtime should be reasonable

#8 pchainho opened 9 years ago
0
The Runtime must be secured

#7 pchainho opened 9 years ago
0

Previous Next