From e7914d0fad7d5ef26f0c89e8b78b5c7b6a2868f5 Mon Sep 17 00:00:00 2001 From: Sam T Date: Fri, 26 Apr 2013 00:18:53 +0400 Subject: ~ Starting separating protocol and high level api. It will be more convenient to provide high level api and raw protocol separated. In many use cases we don't worry about protocol but need some simple things like track swarm/peer state. So I think it will be better to refactor library in the following way: 1. Network.BitTorrent.Tracker.Protocol, Network.BitTorrent.PeerWire.Protocol For raw protocol definitions, documentation and serialization. 2. Network.BitTorrent.Tracker Network.BitTorrent.PeerWire For convenient API. Though we should not restrict user to in some particular way, so high level api should be flexible enough. In other words: mechanism, not policy/framework. --- network-bittorrent.cabal | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'network-bittorrent.cabal') diff --git a/network-bittorrent.cabal b/network-bittorrent.cabal index 98423512..6494ae6a 100644 --- a/network-bittorrent.cabal +++ b/network-bittorrent.cabal @@ -28,6 +28,7 @@ library , Network.BitTorrent.PeerID , Network.BitTorrent.Tracker + , Network.BitTorrent.Tracker.Protocol , Network.BitTorrent.Tracker.Scrape , Network.BitTorrent.PeerWire @@ -40,14 +41,15 @@ library build-depends: - base == 4.* + base == 4.* + , stm >= 2.4 -- Data packages - , bytestring >= 0.10.2.0 + , bytestring >= 0.10.2 , containers >= 0.4 - , text >= 0.11.0.0 + , text >= 0.11.0 - -- encoding/serializations packages + -- encoding/serialization packages , bencoding >= 0.1 , cereal >= 0.3 , urlencoded >= 0.4 @@ -63,6 +65,7 @@ library , filepath == 1.* + extensions: PatternGuards hs-source-dirs: src -- ghc-options: -Wall -- cgit v1.2.3