<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="client.xsl" type="text/xsl"?>
<article article-type="other">
<front>
<journal-meta>
<journal-id/>
<issn/>
<banner>
<!--<href>banner.jpg</href>-->
<size width="100%"/>
</banner>
</journal-meta>
<article-meta>
<title-group>
<article-title>Towards Reflective Mobile Agents for Resource-Constrained Mobile Devices</article-title>
</title-group>

<author><a href="mailto:conor.muldoon@ucd.ie"><name>Conor Muldoon</name></a></author>
<aff>School of Computer Science and Informatics, Belfield, Dublin, 4, Ireland</aff>

<author><a href="mailto:gregory.ohare@ucd.ie"><name>Gregory M.P. O'Hare</name></a></author>
<aff>Adaptive Information Cluster (AIC), School of Computer Science and Informatics, Belfield, Dublin, 4, Ireland</aff>

<author><a href="mailto:john.bradley@ucd.ie"><name>John F. Bradley</name></a></author><aff>School of Computer Science and Informatics, Belfield, Dublin, 4, Ireland</aff>

</article-meta></front>
<body>
<abstract>
<title>ABSTRACT</title>
<p>The vision of ubiquitous computing is one in which resource constrained mobile devices form ad-hoc networks to enable the delivery of services that are sensitive and esponsive to people. Such networks are dynamic and must be capable of dealing with uncertain information. As emergent system behaviour begins to evolve the complexity of pervasive systems increases. The agent development community have been addressing issues of complexity and uncertainty, within distributed computing, for several years. This paper details the migration process of Agent Factory Micro Edition (AFME), a minimised footprint agent platform for resource constrained mobile devices. The process enables agents to migrate from a resource rich environment to a resource constrained mobile device and vice versa. It requires agents to dynamically alter their form and behaviour so as to adapt to their <italic>context</italic>.
</p>
</abstract>
<fpdf>
<href>pdflogo.jpg</href>
<hpdf>AAMAS07_0457_7d15b04eb48ac3a34ca708eedf9ca031</hpdf>
</fpdf>
</body>
</article>

