routing 0.0.9

This is Pre alpha, and not useful, no code worth looking at.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

// Copyright 2015 MaidSafe.net limited
//
// This MaidSafe Software is licensed to you under (1) the MaidSafe.net Commercial License, version
// 1.0 or later, or (2) The General Public License (GPL), version 3, depending on which licence you
// accepted on initial access to the Software (the "Licences").
//
// By contributing code to the MaidSafe Software, or to this project generally, you agree to be
// bound by the terms of the MaidSafe Contributor Agreement, version 1.0, found in the root
// directory of this project at LICENSE, COPYING and CONTRIBUTOR respectively and also available at
// http://maidsafe.net/licenses
//
// Unless required by applicable law or agreed to in writing, the MaidSafe Software distributed
// under the GPL Licence is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
// KIND, either express or implied.
//
// See the Licences for the specific language governing permissions and limitations relating to use
// of the MaidSafe Software.

/// This trait require to be avauilable for any type
/// passed to routing, refresh / account transfer is optional
/// The name will let routing know its an NaeManager and the owner will allow routing to hash
/// the requsters id with this name (by hashing the requesters id) for put and post messages
use name_type;

pub trait MessageInterface {
    fn get_name(&self)->name_type::NameType;
    fn get_owner(&self)->Option<Vec<u8>> { Option::None }
    fn refresh(&self)->bool { false } // is this an account transfer type
    fn merge(&self)->bool { false } // how do we merge these
}