Home > Research > Publications & Outputs > ReMMoC: A Reflective Middleware to Support Mobi...

Electronic data

View graph of relations

ReMMoC: A Reflective Middleware to Support Mobile Client Interoperability

Research output: Contribution to conference - Without ISBN/ISSN Conference paperpeer-review

Published

Standard

ReMMoC: A Reflective Middleware to Support Mobile Client Interoperability. / Grace, P.; Blair, Gordon S.; Samuel, S.
2003. 1170-1187 Paper presented at The 5th International Symposium on Distributed Objects and Applications (DOA 2003).

Research output: Contribution to conference - Without ISBN/ISSN Conference paperpeer-review

Harvard

Grace, P, Blair, GS & Samuel, S 2003, 'ReMMoC: A Reflective Middleware to Support Mobile Client Interoperability', Paper presented at The 5th International Symposium on Distributed Objects and Applications (DOA 2003), 1/01/00 pp. 1170-1187.

APA

Grace, P., Blair, G. S., & Samuel, S. (2003). ReMMoC: A Reflective Middleware to Support Mobile Client Interoperability. 1170-1187. Paper presented at The 5th International Symposium on Distributed Objects and Applications (DOA 2003).

Vancouver

Grace P, Blair GS, Samuel S. ReMMoC: A Reflective Middleware to Support Mobile Client Interoperability. 2003. Paper presented at The 5th International Symposium on Distributed Objects and Applications (DOA 2003).

Author

Grace, P. ; Blair, Gordon S. ; Samuel, S. / ReMMoC: A Reflective Middleware to Support Mobile Client Interoperability. Paper presented at The 5th International Symposium on Distributed Objects and Applications (DOA 2003).18 p.

Bibtex

@conference{6fa3808bee6449f38cc4429c9ade1fab,
title = "ReMMoC: A Reflective Middleware to Support Mobile Client Interoperability",
abstract = "Mobile client applications must discover and interoperate with application services available to them at their present location. However, these services will be developed upon a range of middleware types (e.g. RMI and publish-subscribe) and advertised using different service discovery protocols (e.g. UPnP and SLP) unknown to the application developer. Therefore, a middleware platform supporting mobile client applications should ideally adapt its behaviour to interoperate with any type of discovered service. Furthermore, these applications should be developed independently from particular middleware implementations, as the interaction type is unknown until run-time. This paper presents ReMMoC, a reflective middleware platform that dynamically adapts both its binding and discovery protocol to allow interoperation with heterogeneous services. Furthermore, we present the ReMMoC programming model, which is based upon the Web Services concept of abstract services. We evaluate this work in terms of supporting mobile application development and the memory footprint cost of utilising reflection to create a mobile middleware platform.",
keywords = "cs_eprint_id, 1713 cs_uid, 361",
author = "P. Grace and Blair, {Gordon S.} and S. Samuel",
year = "2003",
month = nov,
language = "English",
pages = "1170--1187",
note = "The 5th International Symposium on Distributed Objects and Applications (DOA 2003) ; Conference date: 01-01-1900",

}

RIS

TY - CONF

T1 - ReMMoC: A Reflective Middleware to Support Mobile Client Interoperability

AU - Grace, P.

AU - Blair, Gordon S.

AU - Samuel, S.

PY - 2003/11

Y1 - 2003/11

N2 - Mobile client applications must discover and interoperate with application services available to them at their present location. However, these services will be developed upon a range of middleware types (e.g. RMI and publish-subscribe) and advertised using different service discovery protocols (e.g. UPnP and SLP) unknown to the application developer. Therefore, a middleware platform supporting mobile client applications should ideally adapt its behaviour to interoperate with any type of discovered service. Furthermore, these applications should be developed independently from particular middleware implementations, as the interaction type is unknown until run-time. This paper presents ReMMoC, a reflective middleware platform that dynamically adapts both its binding and discovery protocol to allow interoperation with heterogeneous services. Furthermore, we present the ReMMoC programming model, which is based upon the Web Services concept of abstract services. We evaluate this work in terms of supporting mobile application development and the memory footprint cost of utilising reflection to create a mobile middleware platform.

AB - Mobile client applications must discover and interoperate with application services available to them at their present location. However, these services will be developed upon a range of middleware types (e.g. RMI and publish-subscribe) and advertised using different service discovery protocols (e.g. UPnP and SLP) unknown to the application developer. Therefore, a middleware platform supporting mobile client applications should ideally adapt its behaviour to interoperate with any type of discovered service. Furthermore, these applications should be developed independently from particular middleware implementations, as the interaction type is unknown until run-time. This paper presents ReMMoC, a reflective middleware platform that dynamically adapts both its binding and discovery protocol to allow interoperation with heterogeneous services. Furthermore, we present the ReMMoC programming model, which is based upon the Web Services concept of abstract services. We evaluate this work in terms of supporting mobile application development and the memory footprint cost of utilising reflection to create a mobile middleware platform.

KW - cs_eprint_id

KW - 1713 cs_uid

KW - 361

M3 - Conference paper

SP - 1170

EP - 1187

T2 - The 5th International Symposium on Distributed Objects and Applications (DOA 2003)

Y2 - 1 January 1900

ER -