- Sky
- Blueberry
- Slate
- Blackcurrant
- Watermelon
- Strawberry
- Orange
- Banana
- Apple
- Emerald
- Chocolate
- Charcoal
Search the Community
Showing results for tags 'ocranet'.
Found 5 results
-
OHML being complete, it just needed something next so the OHML specification is complete. And this thing is what is here: OHTP Definitions: Host - Any computer or machine with a OC-compatible modem attached to it Server - Host sending OHTP-valid data when an user attemps to connect Client - Host receiving OHTP-valid data from a Server OHTP - Open Hyper Text Protocol - Protocol used to transmit OHML - Open Hypertext Markup Language between Hosts. Line Break - Unix style line break: line feed (\n) Specifications: The OHTP protocol doesn't take care of what
-
OHML v1.0.3 OHML is a markup language based on the eXtensible Markup Language (XML), it is a simpler and OC-graphics adapted version of HTML. Why OHML? It all started when i noticed that most network programs/libraries were either DNS system, or Website system. However it is very important to maintain an universal language for webpages. It is the first step of having a stable and universal "OCranet", which will follow with server and client implementations. Protocols, etc.. Concepts HRef: Shortcut for Hyperlink Reference Document Versions OHML patch versions
- 3 replies
-
- 1
-
-
- ocranet
- opencomputers
- (and 1 more)
-
Globally Engineered Routing Technology (GERT) is a networking protocol for OpenComputers that can network OC computers together, and connect different MC servers together via the Internet. It is also capable of linking real life computers to OC Computers. It uses an IPv4-like addressing scheme for computers, which helps generate easier to remember addresses, and it supports both socket and connectionless data transfer methods. More information can be found at https://github.com/GlobalEmpire/GERT/wiki/GERTi For more questions, please either post in this thread, or message MajGenRelati -
The following document is a DRAFT. Any information here may be revised at any time, and suggestions are more than welcome. Rev. #2017010401 (0.1.1) Abstract This draft defines the NNR (Network to Network Routing) protocol as part of the OCranet family of protocols. This document outlines how dynamic routing holds networks together in an NNR enabled OCranet network, how signalling is performed to control these networks, and the format of addressing used. This protocol is NOT the base protocol for OCranet networksand REQUIRES the support of specifications detailed in OETF #4; OCR -
The following document is a DRAFT. Any information here may be revised at any time, and suggestions are more than welcome. Rev. #2017032401 (0.2.0) Abstract This draft defines the OCR (OCranet Relay) protocol as part of the OCranet family of protocols. This document outlines how OCR forms connections, how data is fowarded, and the structure of a data segment used in an OCR network. Rationale An agreement between computers in terms of how to communicate is important in any data network. In the past, there have been several attempts to build networks to transfer data be
