Skip to content
Sign in
Success

SensiNact Northbound REST (Aug 8, 2024, 11:01:54 AM)

Started 1 yr 11 mo ago
Took 12 sec
Build Artifacts
rest-0.0.2-SNAPSHOT-tests.jar39.10 KiB view
rest-0.0.2-SNAPSHOT.jar23.11 KiB view
rest-0.0.2-SNAPSHOT.pom7.46 KiB view
Include the model name in topic notifications

Filtering at the model level is extremely useful as it permits efficient tracking of multiple providers using the same model. The model URI is required to ensure strict uniqueness, however the model uri is difficult to represent in topic syntax, and would need large amounts of escaping. The trade off is therefore to allow the model name to be used in the topic for rapid checking, with the filter being available for more precise matching if needed.

Signed-off-by: Tim Ward <timothyjward@apache.org>
(commit: 9d68852)
timothyjward at
Changes in dependency
  1. SensiNact Northbound Filters :: LDAP #30 → #31 (detail)
  2. SensiNact core Annotations #30 → #31 (detail)
  3. SensiNact internal Metadata Model #30 → #31 (detail)
  4. SensiNact core API with EMF dependencies #30 → #31 (detail)
  5. SensiNact Northbound Query Handler #30 → #31 (detail)
  6. SensiNact Northbound Session Provider #30 → #31 (detail)
  7. SensiNact core implementation #30 → #31 (detail)
  8. SensiNact Northbound Session API #30 → #31 (detail)
  9. SensiNact GeoJSON mapping types #30 → #31 (detail)
  10. SensiNact Provider Model #30 → #31 (detail)
  11. SensiNact internal Testdata Model #30 → #31 (detail)
  12. SensiNact Northbound Filters :: Core #30 → #31 (detail)
  13. SensiNact Northbound Security API #30 → #31 (detail)
  14. SensiNact core API #30 → #31 (detail)