Home > Research > Publications & Outputs > Juno
View graph of relations

Juno: a middleware platform for supporting delivery-centric applications

Research output: Contribution to Journal/MagazineJournal articlepeer-review

Published

Standard

Juno: a middleware platform for supporting delivery-centric applications. / Tyson, Gareth; Mauthe, Andreas; Kaune, Sebastian et al.
In: ACM Transactions on Internet Technology, Vol. 12, No. 2, 4, 02.2012.

Research output: Contribution to Journal/MagazineJournal articlepeer-review

Harvard

Tyson, G, Mauthe, A, Kaune, S, Grace, P, Taweel, A & Plagemann, T 2012, 'Juno: a middleware platform for supporting delivery-centric applications', ACM Transactions on Internet Technology, vol. 12, no. 2, 4. https://doi.org/10.1145/2390209.2390210

APA

Tyson, G., Mauthe, A., Kaune, S., Grace, P., Taweel, A., & Plagemann, T. (2012). Juno: a middleware platform for supporting delivery-centric applications. ACM Transactions on Internet Technology, 12(2), Article 4. https://doi.org/10.1145/2390209.2390210

Vancouver

Tyson G, Mauthe A, Kaune S, Grace P, Taweel A, Plagemann T. Juno: a middleware platform for supporting delivery-centric applications. ACM Transactions on Internet Technology. 2012 Feb;12(2):4. doi: 10.1145/2390209.2390210

Author

Tyson, Gareth ; Mauthe, Andreas ; Kaune, Sebastian et al. / Juno : a middleware platform for supporting delivery-centric applications. In: ACM Transactions on Internet Technology. 2012 ; Vol. 12, No. 2.

Bibtex

@article{b2bb2433f19d47208c724017d2dccc09,
title = "Juno: a middleware platform for supporting delivery-centric applications",
abstract = "This article proposes a new delivery-centric abstraction which extends the existing content-centric networking API. A delivery-centric abstraction allows applications to generate content requests agnostic to location or protocol, with the additional ability to stipulate high-level requirements regarding such things as performance, security, and resource consumption. Fulfilling these requirements, however, is complex as often the ability of a provider to satisfy requirements will vary between different consumers and over time. Therefore, we argue that it is vital to manage this variance to ensure an application fulfils its needs. To this end, we present the Juno middleware, which implements delivery-centric support using a reconfigurable software architecture to: (i) discover multiple sources of an item of content; (ii) model each source{\textquoteright}s ability to provide the content; then (iii) adapt to interact with the source(s) that can best fulfil the application{\textquoteright}s requirements. Juno therefore utilizes existing providers in a backwards compatible way, supporting immediate deployment. This article evaluates Juno using Emulab to validate its ability to adapt to its environment.",
author = "Gareth Tyson and Andreas Mauthe and Sebastian Kaune and Paul Grace and Abdel Taweel and T. Plagemann",
year = "2012",
month = feb,
doi = "10.1145/2390209.2390210",
language = "English",
volume = "12",
journal = "ACM Transactions on Internet Technology",
issn = "1557-6051",
publisher = "ASSOC COMPUTING MACHINERY",
number = "2",

}

RIS

TY - JOUR

T1 - Juno

T2 - a middleware platform for supporting delivery-centric applications

AU - Tyson, Gareth

AU - Mauthe, Andreas

AU - Kaune, Sebastian

AU - Grace, Paul

AU - Taweel, Abdel

AU - Plagemann, T.

PY - 2012/2

Y1 - 2012/2

N2 - This article proposes a new delivery-centric abstraction which extends the existing content-centric networking API. A delivery-centric abstraction allows applications to generate content requests agnostic to location or protocol, with the additional ability to stipulate high-level requirements regarding such things as performance, security, and resource consumption. Fulfilling these requirements, however, is complex as often the ability of a provider to satisfy requirements will vary between different consumers and over time. Therefore, we argue that it is vital to manage this variance to ensure an application fulfils its needs. To this end, we present the Juno middleware, which implements delivery-centric support using a reconfigurable software architecture to: (i) discover multiple sources of an item of content; (ii) model each source’s ability to provide the content; then (iii) adapt to interact with the source(s) that can best fulfil the application’s requirements. Juno therefore utilizes existing providers in a backwards compatible way, supporting immediate deployment. This article evaluates Juno using Emulab to validate its ability to adapt to its environment.

AB - This article proposes a new delivery-centric abstraction which extends the existing content-centric networking API. A delivery-centric abstraction allows applications to generate content requests agnostic to location or protocol, with the additional ability to stipulate high-level requirements regarding such things as performance, security, and resource consumption. Fulfilling these requirements, however, is complex as often the ability of a provider to satisfy requirements will vary between different consumers and over time. Therefore, we argue that it is vital to manage this variance to ensure an application fulfils its needs. To this end, we present the Juno middleware, which implements delivery-centric support using a reconfigurable software architecture to: (i) discover multiple sources of an item of content; (ii) model each source’s ability to provide the content; then (iii) adapt to interact with the source(s) that can best fulfil the application’s requirements. Juno therefore utilizes existing providers in a backwards compatible way, supporting immediate deployment. This article evaluates Juno using Emulab to validate its ability to adapt to its environment.

UR - http://www.scopus.com/inward/record.url?scp=84877942345&partnerID=8YFLogxK

U2 - 10.1145/2390209.2390210

DO - 10.1145/2390209.2390210

M3 - Journal article

AN - SCOPUS:84877942345

VL - 12

JO - ACM Transactions on Internet Technology

JF - ACM Transactions on Internet Technology

SN - 1557-6051

IS - 2

M1 - 4

ER -