Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 32E8C9F40 for ; Sat, 3 Mar 2012 16:14:05 +0000 (UTC) Received: (qmail 21234 invoked by uid 500); 3 Mar 2012 16:14:04 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 21104 invoked by uid 500); 3 Mar 2012 16:14:04 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 21094 invoked by uid 99); 3 Mar 2012 16:14:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Mar 2012 16:14:04 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of simone.tripodi@gmail.com designates 209.85.216.179 as permitted sender) Received: from [209.85.216.179] (HELO mail-qy0-f179.google.com) (209.85.216.179) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Mar 2012 16:13:58 +0000 Received: by qcha6 with SMTP id a6so1050585qch.38 for ; Sat, 03 Mar 2012 08:13:38 -0800 (PST) Received-SPF: pass (google.com: domain of simone.tripodi@gmail.com designates 10.224.177.145 as permitted sender) client-ip=10.224.177.145; Authentication-Results: mr.google.com; spf=pass (google.com: domain of simone.tripodi@gmail.com designates 10.224.177.145 as permitted sender) smtp.mail=simone.tripodi@gmail.com; dkim=pass header.i=simone.tripodi@gmail.com Received: from mr.google.com ([10.224.177.145]) by 10.224.177.145 with SMTP id bi17mr8191564qab.17.1330791218163 (num_hops = 1); Sat, 03 Mar 2012 08:13:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=BGRyZ9S119+yqDHqUOxlJsTLYd8QVNapxQRgEdLaJNM=; b=j+Y+SusHvPt09f16Tkxf42f+Az7gJACl47TSc9fOWeFWlFvoo5di863nHaVe/TYewA zQpR+8yn2uAYVzZfPnMj0/yaCt9aRQuIyodiAIIaTtOm69V/Dxt7e6VwwJbY3n6HHbLD /3Gj0wGAMPfrYb9KwK1g49laYWj+XDXVkoiJrCbnJJsx/2tNknwkG+N0Ckph2Mgy7h/g m6eDMjmkOapcuZIkyLqkMj+ZVixZ/trmZxbcxAU02m1Sc7BxRJND12becSiRk02LUAcH 2Ovr5RhGbJDlvNqkvF6GN1sUfMFOZU7TWVdG70uxzbn6NtVzI/8VFVoEQphLLB9aEB/9 Fpjw== MIME-Version: 1.0 Received: by 10.224.177.145 with SMTP id bi17mr6892623qab.17.1330791218101; Sat, 03 Mar 2012 08:13:38 -0800 (PST) Sender: simone.tripodi@gmail.com Received: by 10.224.195.73 with HTTP; Sat, 3 Mar 2012 08:13:38 -0800 (PST) In-Reply-To: <4F5242BF.6080205@dia.uniroma3.it> References: <4F508774.7080905@dia.uniroma3.it> <4F513A1F.1030103@dia.uniroma3.it> <4F5167CB.4060306@dia.uniroma3.it> <4F521202.7010207@dia.uniroma3.it> <4F52236C.9000708@dia.uniroma3.it> <4F5242BF.6080205@dia.uniroma3.it> Date: Sat, 3 Mar 2012 17:13:38 +0100 X-Google-Sender-Auth: jXIDTh11eFErzw_YEHoy678BH8U Message-ID: Subject: Re: [graph] Why the Vertex and Edge interfaces? From: Simone Tripodi To: Commons Developers List Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org please follow up code modifications on SANDBOX-404 http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sat, Mar 3, 2012 at 5:11 PM, Claudio Squarcella wrote: > Hi Simone, > > answering briefly below: > > >> Vertex is something we can safety drop because we >> know its nature at priori, markers are unnecessary.This is fine. > > > +1. > > >> what is the sense, at that point, on keeping the Edge?!! It would be >> more than enough to know which is the Head and which is the Tail in >> the Edge to get the W! > > > good observation. My 2 cents: it might still make sense for users to map > their existing domain (including "edges") to the graph (e.g. Routers to > Vertices and Cables to Edges) and "get it back" as soon as they are done > with graph operations (e.g. once they find the shortest path, they > automatically have the sequence of Cables they need). > >> maybe because they implement OrderedMonoid? :) >> [...] >> >> how much would Addition and Multiplication interface differ each other? >> [...] >> that would be fine, what is not clear is that Monoids expose the same >> interface, so *Operations class implementation canot declare same >> method multiple times > > > answering all the above: that is another reason why I would like our current > Monoid to be called Addition (and Addition#sum instead of Monoid#append, > etc), so that it is semantically clearer and later we can introduce > Multiplication as a completely independent interface. > > >> enough talk IMHO, time to code and make concrete proposals > > > Sure! > I'll play with weights first, because I already know what I want to do. > As for Vertex/Edge markers I still see valuable feedback coming in, so I'll > wait a bit. > > Branching is ok -- especially for the second part which sounds like a real > earthquake ;) > > > Ciao, > Claudio > > -- > Claudio Squarcella > PhD student at Roma Tre University > http://www.dia.uniroma3.it/~squarcel > http://squarcella.com/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org