[Architecture] Matchmaker Technical Meeting, round #5 - Doodle poll
claudia.loitsch at tu-dresden.de
Tue Apr 29 05:53:51 EDT 2014
Hi Andy and Andres,
Andy`s sketch illustrates a possible flow between the mini-matchmaker
and a cloud one. A main extend to our current approach is that a cloud
matchmaker delivers instructions (M3) to the mini matchmaker. The whole
diagram is abstract and does not include how components of the
architecture are involved.
Andres diagram shows a draft how the CAS could be included in the
architecture. It says that there is no direct communication between a
cloud matchmakers and a mini matchmaker. Instead, communication between
both MMs occurs indirect via the flow manager. As far as I know Colin
and you Andres have worked on the integration process while writing the
new architecture deliverable. It would be interesting what are the
results until now.
As both diagrams are different, I think the questions is not which
diagram is preferred ;) The question is rather if we can reduce both
diagrams to a common denominator.
Well, I think we could achieve following decisions in the call later today:
* do we seek a direct communication between cloud-based MMs and the mini
* do we agree on the new output M3 of a cloud-based matchmaker to
instruct the mini matchmaker?
** how could these instructions look like? Do we have already examples?
* As Andy`s diagram is abstract is does not say how cloud-based MMs
receive input (preferences+context). Even if we have discussed this
already, we need a decision if the MMs fetch all required input or if we
keep our current approach which means that cloud-based MMs receive input
Apart from this, I believe we need more real examples workflows that
help us defining payloads and APIs for the following scenarios:
* default: the cloud-based matchmaker delivers M3 instructions for the
* extended: define an example workflow if the mini matchmaker needs to
call a cloud-based matchmaker?
** when does this happen?
** what happens then?
* default: feedback loop - MMs-PCP; MMM-PCP?
* ... to collect more scenarios that need to be sketched up. Lets sum up
a list of functions (workflows) that need to be drafted.
Am 29.04.2014 11:01, schrieb Andrés Iglesias Pérez:
> Hi everyone,
> I still prefer the years old diagram that was showed in
> ) and updated in Madrid
> But maybe that's because every father thinks that their children are
> the prettiest :-P
> This two-sided arrow is a good fit for the new (to me) local flow manager.
> Kind Regards,
> Andrés Iglesias Pérez
> Researcher @ R&D Department, Technosite, Fundosa Group
> C/ Albasanz, 16, 3ºB. 28037. Madrid. Spain
> (0034) 91 121 03 30
> *De:*Andreas Stiegler [mailto:stiegler at hdm-stuttgart.de]
> *Enviado el:* martes, 29 de abril de 2014 10:44
> *Para:* 'Claudia Loitsch'; Andrés Iglesias Pérez; 'Kasper Galschiot
> *CC:* architecture at lists.gpii.net
> *Asunto:* RE: Re: Matchmaker Technical Meeting, round #5 - Doodle poll
> Heyho Claudia,
> Nope didn't forget, just wasn't able to finish it yet :) I prepared a
> diagram with the flow between the mini matchmaker and the cloud one
> Yet, we still have to precisely identify which of these relations we
> really need and how their interaction works. Sorry for the delay! Been
> busy around here.
> Best regards,
> *From:*Claudia Loitsch [mailto:claudia.loitsch at tu-dresden.de]
> *Sent:* Tuesday, April 29, 2014 9:56 AM
> *To:* 'Andreas Stiegler'; Andres Iglesias-Perez; Kasper Galschiot Markus
> *Cc:* architecture at lists.gpii.net <mailto:architecture at lists.gpii.net>
> *Subject:* Fwd: Re: Matchmaker Technical Meeting, round #5 - Doodle poll
> Hi Andy,
> In preparation of today's technical meeting, we had the task to
> concretize MM workflows as a basis to decide on APIs/workflows and
> that we can plan next steps. Did you forget about this task? You
> wanted to send Andres and me first drafts but I did not receive any
> mail from you since our last meeting.
> As it is important that these workflows suits requirements of both
> matchmakers, we cannot discuss/decide on this topic during the meeting
> today unless I (and the RBMM team) had the chance to look at your
> sketches beforehand. Hence, we need to shift this topic at least to
> one week.
> Could you please clarify what is the status of your draft? If you have
> to many thinks on you plate I could take this work over. Just let me
> Best regards,
> -------- Original-Nachricht --------
> *Betreff: *
> Re: Matchmaker Technical Meeting, round #5 - Doodle poll
> *Datum: *
> Tue, 22 Apr 2014 14:57:28 +0200
> *Von: *
> Kasper Markus <kasper at markus.dk> <mailto:kasper at markus.dk>
> *An: *
> Clark, Colin <cclark at ocadu.ca> <mailto:cclark at ocadu.ca>, 'Claudia
> Loitsch' <claudia.loitsch at tu-dresden.de>
> <mailto:claudia.loitsch at tu-dresden.de>, Andrés Iglesias Pérez
> <aiglesias at technosite.es> <mailto:aiglesias at technosite.es>, Andreas
> Stiegler <stiegler at hdm-stuttgart.de>
> <mailto:stiegler at hdm-stuttgart.de>, Nikos Kaklanis <nkak at iti.gr>
> <mailto:nkak at iti.gr>, Christophe Strobbe <strobbe at hdm-stuttgart.de>
> <mailto:strobbe at hdm-stuttgart.de>, Joseph Scheuhammer
> <clown at alum.mit.edu> <mailto:clown at alum.mit.edu>, Antranig Basman
> <amb26 at ponder.org.uk> <mailto:amb26 at ponder.org.uk>,
> architecture at lists.gpii.net <mailto:architecture at lists.gpii.net>
> Architecture <architecture at lists.gpii.net>
> <mailto:architecture at lists.gpii.net>, Ignacio Peinado Martínez
> <ipeinado at technosite.es> <mailto:ipeinado at technosite.es>
> Hi Matchmakers,
> Our afternoons is getting tighter and tighter, but there is a timeslot
> available on Tuesday, 29th, 14:00-16:00 CEST (8 AM EST)
> From my previous mail, I think these should still be the goals:
> I think we should aim at getting at some concrete goals, dates and
> plans for everything we've previously discussed during these
> meetings... That'll allow us to incorporate this into the greater
> upcoming C4A roadmap and start implementation.
> A reminder of the tasks that were decided on last time:
> * *Andy, Claudia and Andres:*will work through some specific
> example MM workflows. (andy will sketch them, send them
> around, start discussion asynchronously)
> * *Andres: *Do some sketches of specific conditions, consider
> required types. (send around, start asynchronous discussion)
> We will have the meeting in https://global.gotomeeting.com/join/619028605
> See you then,
> Kasper Galschiot Markus
> Lead Research Engineer,
> Raising the Floor - International,
> www.raisingthefloor.org <http://www.raisingthefloor.org>
Dipl.-Medieninf. Claudia Loitsch
Technische Universität Dresden
Institut für Angewandte Informatik
Professur Mensch-Computer Interaktion
Tel.: 0351/463 42025
Fax: 0351/463 38491
E-Mail: claudia.loitsch at tu-dresden.de
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Architecture