| Name | Modified | Size |
|---|---|---|
| .. | ||
| connect.go | 11 years ago | 6 KB |
| Change | User | Description | Committed |
|---|---|---|---|
| 10478 | Brett Bates | Message formatting only handled a single %replacement%, now does all | 11 years ago |
| 10477 | Brett Bates | The original point in doing this was to try to retrieve a p4 info, so now formats the outp...ut Can get a p4 info request returned :) « |
11 years ago |
| 10476 | Brett Bates | Still just a thought exercise but now uses the length correctly, and composes the request ... The encoder and decoder bits don't really mirror eachother, just wrote the quickest bit of code possible For an actual, non-messy, useful, golike api would make the buffer readers and writers implement their io counterparts, should also be able to create multiple connections, which would return a goroutine with channels for encoding decoding etc. « |
11 years ago |
| 10474 | Brett Bates | The most basic (useful) invoke/dispatch i could fathom for creating a p4 api in golang &n...bsp; Currently just sends out the protocol/user-info call as a byte slice, and reads in the response to a map of type map[string]data where data contains the header and the value Poorly written go, with a very dumb implementation of the protocol, using the 5 byte headers first value as our length... « |
11 years ago |