nfn-scala now supports both the SingleContent and MultiSegmentContent (StreamContent not yet implemented)
- every received data of each content object is first decoded with the CCNLiteContentFormat
- MultiSegmentContent is collected and concatenated internally
- currently the segment component name is appended to the last component instead of its own component to force ccn-lite to send the correct packet
Fixed ordering of concatenated multi segment content and creation of content in compute worker
NFNMasterSpec passes except for tasks where the abstract machine converts content because it does not yet support the content encoding
Added NDNTLVException