<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Erik,<br>
<br>
a list of extended storages sounds interesting, still I would like
to understand better the usecase.<br>
<br>
When you would use e.g. a subclass with separate DataAccess
objects what would be more complex or impossible compared to a
list of extended storages?<br>
<br>
Kind Regards,<br>
Peter.<br>
<br>
On 27.10.2014 22:35, Erik Formella wrote:<br>
</div>
<blockquote
cite="mid:CA+EiZKU7afz=W5eY9Gvdm80zfZvqNTLC9mQXa-76vzUNpfokZg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>It looks like to be able to support turn costs we have to
sacrifice the ability to use any other extended storage.</div>
<div><br>
</div>
<div>I am thinking I can refactor <font face="courier new,
monospace">GraphStorage</font> to use an <font
face="courier new, monospace">ExtendedStorageManager</font>.
It would allow us to write things like:</div>
<div><br>
</div>
<div><font face="courier new, monospace">TurnCostStorage
turnCostStorage =
graph.getExtendedStorageManager().get("turn_costs");</font></div>
<div><br>
</div>
<div>instead of doing:</div>
<div><br>
</div>
<div><font face="courier new, monospace">if
(graph.getExtendedStorage() istanceof TurnCostStorage) { ...
}</font></div>
<div><br>
</div>
<div><br>
</div>
<div>This is just my first guess at what the interfaces should
look like, but does that seem like a change you would
appreciate in GraphHopper?</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
GraphHopper mailing list
<a class="moz-txt-link-abbreviated" href="mailto:GraphHopper@openstreetmap.org">GraphHopper@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/graphhopper">https://lists.openstreetmap.org/listinfo/graphhopper</a>
</pre>
</blockquote>
<br>
</body>
</html>