Merge pull request #24 from jrmcclurg/master

Fixed typo in ports_of_switch function
Update authors to something more accurate
Move abfattree.py to separate experiments repo.
Merge branch 'master' of github.com:frenetic-lang/ocaml-topology
Bugfix to stitch function
no_ofp: Use portId type synonym consistently

Some instances of VInt.t were used instead of portId. For more
documentation-like type signatures, use portId instead.
no_ofp: Use int64 for cost and capacity

Cost and capacity were using the VInt.t type event though they weren't
making use of any of its features. There was one exception where a
VInt.Int16 was constructed for the cost, that seemed unnecessary.
no_ofp: replace addr{MAC,IP} with Packet.{dl,nw}Addr

These types are already defined by the Packet module.
no_ofp: Use int64 for portId

Similar story to cost and capacity. OpenFlow 1.0 support 2^32 ports,
while OpenFlow 1.3 support 2^64 ports. Use the latter so the code works
with both.
no_ofp: Use int64 for switchId

The datapath_id is an int64 across OpenFlow standars, so just use that.
no_ofp: Remove ocaml-openflow as a dependency
Merge pull request #26 from frenetic-lang/no_ofp

Eliminate ocaml-openflow as a dependency
Added slightly faster hand-rolled shortest-path

- Added shortest path implementation slightly faster than ocamlgraph's
- Added Jane Street's Core as a dependency (using their heaps)
- Updated .mli files to expose new shortest path implementation
Removed speed test from oasis
Merge pull request #28 from frenetic-lang/speed-fix

Removed speed test from oasis
travis: use opam-street to setup opam (Fixes build)

Core is now a dependency of ocaml-topology, so add it as such in
.travis.yml and use opam-street in .travis-ci.sh to speed up the build.
Merge pull request #29 from frenetic-lang/travis

travis: use opam-street to setup opam (Fixes build)
Renamed and expanded node attribute type
Separated Node, Link and Topology (now Network) into separate files
intf: add next_hop_via, returns label

the next_hop function tells you what the next node in the graph is, but
many times you want to know how you got there. In particular, you often
want to know which ports on different switches are connected.
next_hop_via allows you to retrieve that information.