Ashwin Sridharan | fd9cc7a | 2019-04-03 16:47:02 -0400 | [diff] [blame] | 1 | # |
| 2 | #================================================================================== |
E. Scott Daniels | b0ba22e | 2019-08-06 13:26:12 -0400 | [diff] [blame] | 3 | # Copyright (c) 2019 Nokia |
Ashwin Sridharan | fd9cc7a | 2019-04-03 16:47:02 -0400 | [diff] [blame] | 4 | # Copyright (c) 2018-2019 AT&T Intellectual Property. |
| 5 | # |
| 6 | # Licensed under the Apache License, Version 2.0 (the "License"); |
| 7 | # you may not use this file except in compliance with the License. |
| 8 | # You may obtain a copy of the License at |
| 9 | # |
| 10 | # http://www.apache.org/licenses/LICENSE-2.0 |
| 11 | # |
| 12 | # Unless required by applicable law or agreed to in writing, software |
| 13 | # distributed under the License is distributed on an "AS IS" BASIS, |
| 14 | # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| 15 | # See the License for the specific language governing permissions and |
| 16 | # limitations under the License. |
| 17 | #================================================================================== |
| 18 | # |
| 19 | |
E. Scott Daniels | 392168d | 2019-11-06 15:12:38 -0500 | [diff] [blame] | 20 | RIC Message Router -- RMR |
Ashwin Sridharan | fd9cc7a | 2019-04-03 16:47:02 -0400 | [diff] [blame] | 21 | |
E. Scott Daniels | 392168d | 2019-11-06 15:12:38 -0500 | [diff] [blame] | 22 | RMR is a message router library which an application can use to send messages |
| 23 | to other RMR based applications. The destination of each message is governed |
| 24 | by the message type and subscription ID, or just the message type. RMR is |
| 25 | responsible for establishing and managing each connection freeing the application |
| 26 | from any network connectivity management. |
Ashwin Sridharan | fd9cc7a | 2019-04-03 16:47:02 -0400 | [diff] [blame] | 27 | |
E. Scott Daniels | 392168d | 2019-11-06 15:12:38 -0500 | [diff] [blame] | 28 | This repo contains the source and documentation for both the core RMR library |
| 29 | and for the Python bindings which allow a Python (v3) application to use RMR |
| 30 | to send and receive messages. |
Ashwin Sridharan | fd9cc7a | 2019-04-03 16:47:02 -0400 | [diff] [blame] | 31 | |
E. Scott Daniels | 392168d | 2019-11-06 15:12:38 -0500 | [diff] [blame] | 32 | The directories at the root level are as follows, each contains its own readme |
| 33 | file where additional details are necessary. |
E. Scott Daniels | b0ba22e | 2019-08-06 13:26:12 -0400 | [diff] [blame] | 34 | |
Ashwin Sridharan | fd9cc7a | 2019-04-03 16:47:02 -0400 | [diff] [blame] | 35 | |
E. Scott Daniels | 392168d | 2019-11-06 15:12:38 -0500 | [diff] [blame] | 36 | ci This directory contains the continuous integration scripts needed |
| 37 | to build and verify RMR when changes are made and committed to the repo. |
Ashwin Sridharan | fd9cc7a | 2019-04-03 16:47:02 -0400 | [diff] [blame] | 38 | |
E. Scott Daniels | 392168d | 2019-11-06 15:12:38 -0500 | [diff] [blame] | 39 | doc RMR documentation is written in a document language and thus is |
| 40 | source code. This directory contains the source for all generated |
| 41 | documentation. |
Ashwin Sridharan | fd9cc7a | 2019-04-03 16:47:02 -0400 | [diff] [blame] | 42 | |
E. Scott Daniels | 392168d | 2019-11-06 15:12:38 -0500 | [diff] [blame] | 43 | docs This is a 'canned' directory which is intended to be scraped. Direct |
| 44 | editing of documentation files in this directory is dangerous as |
| 45 | most of the files, even though checked into the repo per mandate, |
| 46 | are artifacts and will be overlaid if hand edited. |
Ashwin Sridharan | fd9cc7a | 2019-04-03 16:47:02 -0400 | [diff] [blame] | 47 | |
E. Scott Daniels | 392168d | 2019-11-06 15:12:38 -0500 | [diff] [blame] | 48 | examples This directory contains example programmes which illustrate the use |
| 49 | of RMR. |
Ashwin Sridharan | fd9cc7a | 2019-04-03 16:47:02 -0400 | [diff] [blame] | 50 | |
E. Scott Daniels | 392168d | 2019-11-06 15:12:38 -0500 | [diff] [blame] | 51 | ext RMR makes use of NNG (next generation Nanomsg). The ext directory is |
| 52 | the git reference allowing the NNG code to be pulled and built as |
| 53 | a reference. |
Ashwin Sridharan | fd9cc7a | 2019-04-03 16:47:02 -0400 | [diff] [blame] | 54 | |
E. Scott Daniels | 392168d | 2019-11-06 15:12:38 -0500 | [diff] [blame] | 55 | src This directory is the top level source directory containing both the |
| 56 | core RMR code, and any bindings which have been written. |
Ashwin Sridharan | fd9cc7a | 2019-04-03 16:47:02 -0400 | [diff] [blame] | 57 | |
E. Scott Daniels | 392168d | 2019-11-06 15:12:38 -0500 | [diff] [blame] | 58 | test All unit and application level tests for the core library are kept |
| 59 | within this directory. Tests for bindings are managed within the |
| 60 | binding's directory under the source directory. |
E. Scott Daniels | b7a4b52 | 2019-11-07 15:35:17 -0500 | [diff] [blame] | 61 | |
| 62 | Top level pollution |
| 63 | There are several "configuration" files which sit at the top level of the |
| 64 | repo that are required for some sort of CI/CD/Documentation automation. Most, |
| 65 | if not all of the CI/CD goo is in the ci directory where it's out of the way |
| 66 | and thus not confusing. However, there is some pollution that can generally |
| 67 | be ignored: |
| 68 | |
E. Scott Daniels | 9528bb9 | 2019-12-03 14:26:03 -0500 | [diff] [blame] | 69 | tox.ini -- this seems to drive the scraper which pulls from docs and |
E. Scott Daniels | b7a4b52 | 2019-11-07 15:35:17 -0500 | [diff] [blame] | 70 | writes to some external documentation repo/host. |
| 71 | |
E. Scott Daniels | 9528bb9 | 2019-12-03 14:26:03 -0500 | [diff] [blame] | 72 | |
E. Scott Daniels | b7a4b52 | 2019-11-07 15:35:17 -0500 | [diff] [blame] | 73 | .readthedocs.yaml -- this seems to be some configuration for the docs |
| 74 | scraping process(es). |