Consolidate route code

[brycelelbach]

[reported by hkaiser] [Trac time Tue Feb 28 16:15:45 2012] We currently have duplicated code which is a maintenance problem.

The duplication needs to be consolidated in (at least):

• apply
• futures

[brycelelbach]

[comment by blelbach] [Trac time Fri Apr 6 02:34:44 2012] Vinay, status on this?

[brycelelbach]

[comment by vamatya] [Trac time Fri Apr 6 02:48:13 2012] It has not been looked into. I'll start on it.

[brycelelbach]

[comment by hkaiser] [Trac time Tue Apr 24 11:33:05 2012] This should be done by moving the routing code to the parcel layer. This aditionally implies we come up with some metric allowing to decide whether to route or not.

Another solution to replace the current scheme with routing alltogether would be to make sure that routing does not introduce any significant serialization overheads for large (payload-) parcels. One possibility would be to store parcels as payload in the wrapping routing parcel in form of a unstructured byte sequence. This would prevent deserialization/serialization of the embedded parcel on the AGAS server node.

[brycelelbach]

Vinay, can you please look into this? This has been opened for more than 6 months.

[vamatya]

Bryce, I'm working on metrics. As soon as I'm done with metric system, I'll consolidate the route code

[brycelelbach]

Please make this a priority, it's important that you wrap up this work.

[hkaiser]

This has been fixed while implementing the distributed AGAS (see #177: Implement distributed AGAS)