Data Channel

Serializing and deserializing data in our network test harness is too much work. We simplify the code to handle arbitrary objects, which opens up the opportunity to have a generic data channel. Making it work requires our test harness server to centralize data parsing, so we work on that refactoring. The code’s cleaning up nicely.

  1. E422Back to Networking

    Wed, 22 June ’16
  2. E423Digging Into the Network Tests

    Mon, 27 June ’16
  3. E424Our Little Socket.IO Server

    Wed, 29 June ’16
  4. E425Cohesion

    Mon, 4 July ’16
  5. E426Encapsulation

    Wed, 6 July ’16
  6. E427Simplifying the Test Harness Client

    Mon, 11 July ’16
  7. E428Send Pointer Location

    Wed, 13 July ’16
  8. E429Rethinking the Network Event API

    Mon, 18 July ’16
  9. E430Serving the Unique ID

    Wed, 20 July ’16
  10. E431Data Channel

    Mon, 25 July ’16
  11. E432File Factor

    Wed, 27 July ’16