pdf - 395 K - Ecole des mines de Nantes

More documents

Recommendations

Info

Agent1A1 CM1 CAgent2MQStep 1: Activity A1 of Agent1 creates a conversation C which is immediately considered as handledby Agent1 (grey color). A message M1 is sent by A1 to agent Agent2 in the context of C. Thus A1expects a reply in the context of C (dotted thread arrow) and a clone of C is embedded in M1. Theclone is not considered as handled by Agent2 (white color), hence it is normally stored in Agent2’smessage queue MQ.Agent1Agent2A1CA2 CStep 2: An activity A2 handles M1 in Agent2 and gets the non-handled conversation.Agent1Agent2A1CM2CA2 CStep 3: A2 sends a reply M2 to Agent1 in the context of C. C is thus considered as handled byAgent2. M2 is obtained directly by A1, bypassing Agent1’s message queue, since C is handled byAgent1. As C is considered handled by both agents, A1 and A2 can do synchronized andasynchronous exchanges of messages.Principle of conversationsA conversation finishes in two cases. First, it is possible to send a message and do not expectany reply. All replies will be ignored since the messages are not stored in the agent’s messagequeue. Secondly, a conversation can be simply closed, which has the same effect.MSc EMOOSE Thesis – http://www.emn.fr/EMOOSE 43
4 Application level4.1 OverviewThe figure at the end of this section shows an overview of the agents that have to beimplemented and the status of the implementation. I did part of the implementation, anotherpart has been affected to another team member and a last part has not been implemented yet.Below is the description of the part I have implemented.4.2 User Agent ProxyThe singleton User Agent Proxy receives 2 kinds of messages:(1) navigation messages from the Web Log Monitor that are notifications of accesses.This is for notifying User Agents;(2) termination request messages from User Agents. This happens when a User Agentconsiders that the user it handles has stopped using the Navigation System after acertain time. The User Agent Proxy decides whether to give termination authorizationor not.Therefore the behaviour of the main thread of the User Agent Proxy is described as follows:initialize()WaitingnavigationMessageArrived()InitiatingNavigationHandling ActivityterminationRequestMessageArrived()Initiating TerminationExaminationActivityStatechart diagram of the main thread of the User Agent ProxyEach time a new message arrives, a new activity is created for handling it. This is because alot of messages are likely to be sent to the User Agent Proxy. It was thus chosen to performconcurrent computation of the messages.4.2.1 Navigation message handlingWhen a notification about an access is received as a navigation message, 3 configurations arepossible depending on the state of the User Agent that handles the user of the access:- The User Agent is currently available: the message is forwarded to it.- No User Agent handles the user: its creation is requested to the User Agent Makeragent. An acknowledgement is received in the context of a conversation when theUser Agent is ready to handle messages. In the meantime, a temporary queue iscreated for keeping all the messages that should be handled by the User Agent. WhenMSc EMOOSE Thesis – http://www.emn.fr/EMOOSE 44
Page 1: Vrije Universiteit Brussel - Belgiu
Page 4 and 5: ContentsAbstract 1Acknowledgements
Page 6 and 7: (4) Table UP_SUP (matches User Prof
Page 9 and 10: content providers’ interpretation
Page 11 and 12: - Active profiling consists in aski
Page 13 and 14: 2 Agents2.1 Overview2.1.1 Definitio
Page 15 and 16: (1) each agent has incomplete infor
Page 17 and 18: MASs need an organization for speci
Page 19 and 20: However, the usefulness of personal
Page 21 and 22: they often provide implementation o
Page 23 and 24: 2.5 Design2.5.1 The DIMA designIn [
Page 25 and 26: 3 MetadataDuring the earlier invest
Page 27 and 28: This requires some agreement and st
Page 29 and 30: 4 PerspectivesRecommender systems m
Page 31 and 32: way Lego blocks should be assembled
Page 33 and 34: usiness intelligence is generated.
Page 35 and 36: important than memory space optimiz
Page 37 and 38: The graph is then formatted to be v
Page 39 and 40: Chapter 4: Implementation1 Implemen
Page 41 and 42: (1) A Name Server (NS) maps every a
Page 43: the agent terminates, the thread is
Page 47 and 48: 4.3 User Agent MakerThis agent has
Page 49 and 50: Thus the profile, node and link cla
Page 51 and 52: BIProviderR : Provide_Business_Inte
Page 53 and 54: to enable users to explicitly speci
Page 55 and 56: ConclusionA “minimalist” approa
Page 57 and 58: Appendix A: Addendum onIndustrial I
Page 59 and 60: Appendix B: SQL Tables Design1 Tabl
Page 61 and 62: Appendix C: Conference PaperA paper
Page 63 and 64: very large repositories of learning
Page 65 and 66: popularity of the link (the bigger
Page 67 and 68: Appendix D: Source Code1 Agent infr
Page 69 and 70: public static bool ProcessIsMainHos
Page 71 and 72: string path = MakePath(".", Middlew
Page 73 and 74: System.Messaging.MessageQueue queue
Page 75 and 76: public static NameServer GetNS(){if
Page 77 and 78: }}}table[agentId] = address;}}/// /
Page 79 and 80: ****** NON-STATIC PART ******// Tab
Page 82 and 83: }}}return (AgentId) first;using Sys
Page 85 and 86: {}return Subject.GetHashCode() + Na
Page 87 and 88: name in order to allow for the retr
Page 89 and 90: }// Start agent's main Thread.Threa
Page 91 and 92: }DirectoryFacilitator.GetDF().Unreg
Page 93 and 94: {/// /// Allows for specific conver
Page 95 and 96:
}Monitor.Exit(aLock);public overrid
Page 97 and 98:
Allows for synchronized Message exc
Page 99 and 100:
esource./// /// public string GetMa
Page 101 and 102:
}}private void RunTerminationExamin
Page 103 and 104:
}private Message RequestUACreation(
Page 105 and 106:
}msgQueue.AddFilters(new MessageCat
Page 107 and 108:
Message received: interrupt preterm
Page 109 and 110:
19. Class Architecture.DBManagerAg
Page 111 and 112:
}}connection.Close();/// /// For sa
Page 113 and 114:
using System.Collections;namespace
Page 115 and 116:
namespace Architecture.Profiles{usi
Page 117 and 118:
private UP(DataRow row) : this(newU
Page 119 and 120:
}DataRow[] rows = Row.GetChildRows(
Page 121 and 122:
}adapter.Update(Data);//***********
Page 123 and 124:
internal static readonly string LAS
Page 125 and 126:
}}Row[OCCURRENCES] = Occurrences +
Page 127 and 128:
}get{}return Data.Rows.Find(_name);
Page 129 and 130:
private static SqlDataAdapter adapt
Page 131 and 132:
}foreach (ILink link in links){if (
Page 133 and 134:
}}}private DataRow Row{get{return D
Page 135 and 136:
18. N. Good, et al. Combining colla
Page 137 and 138:
49. D. Derbyshire, et al., Agent-Ba
Page 139:
83. Council for Higher Education Ac
show all

pdf - 395 K - Ecole des mines de Nantes

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?