Jump to content
  • Sky
  • Blueberry
  • Slate
  • Blackcurrant
  • Watermelon
  • Strawberry
  • Orange
  • Banana
  • Apple
  • Emerald
  • Chocolate
  • Charcoal

skyem123

Members
  • Content Count

    22
  • Joined

  • Last visited

  • Days Won

    3

skyem123 last won the day on February 28 2017

skyem123 had the most liked content!

About skyem123

  • Rank
    Junior Member

Profile Information

  • Gender
    Male
  • Interests
    Computers, Minecraft, old computers, computers in Minecraft, openTTD (I once crashed their website, oops!).

Contact Methods

  • Minecraft
    skyem123
  • GitHub
    skyem123

Recent Profile Visitors

927 profile views
  1. Well someone else can make a standard using CBOR. I won't steal their thunder, though I recommend to whoever does it, use a structure similar to this. ^^;
  2. I chose MessagePack because I didn't think about or see the other thing. Maybe another thing would be "better", but there's a point where you just have to pick something, and theoretically you could use a similar method on other ways to encode / store tables. For example, this could be done with the OpenOS table serialise function for extra inefficiency, however this specific standard uses MessagePack.
  3. It's very hard to convert Markdown into what this forum uses, so the specification and example implementation is in a gist: https://gist.github.com/skyem123/f5aa955699da26a5b8b9a6390552232a I may change the wording or fix bugs, but the actual specification will not / should not change.
  4. That's good to know, I'd say one port is better, especially if the users want to change it / remap it.
  5. Why does GERT need 172 ports? That seems a bit too many. Theoretically you can stuff it all into one port, and have your own system for "sub" ports? I dunno, but it would probably be better/nicer if it only needed one port?
  6. I see... it would make automatic configuration systems harder in general though.
  7. For the record, it should not be a guide on how to use it, and while your white-paper does explain the protocol, has unnecessary advertising for it at the start. Don't advertise, just describe how it works and why things are the way they are.
  8. I'm reading this, and while it does seem like a good idea, using the port number as some sort of VLAN seems to conflict with other services and you using port 1. Also, I am a bit worried about using port 1, as while it's a good number, someone earlier could have used it?
  9. No... not a video. A text document describing technical details, like an RFC on the IETF.
  10. First off, this formatting is terrible. While I'm being nitpicky, this is standard thing rather than an advertising thing, so maybe don't describe why you think it's awesome, instead, focus on explanations of the protocol with neat graphics. Anyway, it is good that you have explained how your protocol works in a step by step way.
  11. I kinda want to work on miniOS, but I have lost my motivation

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.