Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [RFC v3 16/16] elect: Add documentation
Date: Wed, 14 Dec 2011 19:10:55 -0600	[thread overview]
Message-ID: <4EE9491F.50709@gmail.com> (raw)
In-Reply-To: <1323788410-9988-17-git-send-email-wagi@monom.org>

[-- Attachment #1: Type: text/plain, Size: 3454 bytes --]

Hi Daniel,

On 12/13/2011 09:00 AM, Daniel Wagner wrote:
> From: Daniel Wagner <daniel.wagner@bmw-carit.de>
> 
> ---
>  doc/elect-api.txt |   86 +++++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 files changed, 86 insertions(+), 0 deletions(-)
>  create mode 100644 doc/elect-api.txt

Logically this patch should probably be amongst the first, not dead last ;)

> 
> diff --git a/doc/elect-api.txt b/doc/elect-api.txt
> new file mode 100644
> index 0000000..a603266
> --- /dev/null
> +++ b/doc/elect-api.txt
> @@ -0,0 +1,86 @@
> +
> +Manager hierarchy
> +=================
> +
> +Service		org.ofono.elect
> +Interface	org.ofono.elect.Manager

Any particular reason why the project is named 'elect'?

> +Object path	/
> +
> +Methods		array{object,dict} GetDevices()
> +
> +			Get an array of device objects and properties
> +			that represent the currently attached devices.
> +
> +			This method call should only be used once when an
> +			application starts up. Further device additions
> +			and removal shall be monitored via DeviceAdded and
> +			DeviceRemoved signals.
> +
> +Signals		DeviceAdded(object path, dict properties)
> +
> +			Signal that is sent when a new device is added.  It
> +			contains the object path of new device and its
> +			properties.
> +
> +		DeviceRemoved(object path)
> +
> +			Signal that is sent when a device has been removed.
> +			The object path is no longer accessible after this
> +			signal and only emitted for reference.
> +
> +
> +Device hierarchy
> +================
> +
> +Service		org.ofono.elect
> +Interface	org.ofono.elect.Device
> +Object path	/{device0,device1,...}
> +
> +Methods		dict GetProperties()
> +
> +			Returns properties for the device object. See
> +			the properties section for available properties.
> +
> +Signals		PropertyChanged(string name, variant value)
> +
> +			This signal indicates a changed value of the given
> +			property.
> +
> +Properties	string Name [readonly]
> +
> +			Friendly name of the device.
> +
> +		boolean Active [readwrite]
> +
> +			Holds whether the device is connected. A
> +			connection will be established when this value
> +			is set to true. A existing connection will be
> +			teared down when set to false.
> +
> +		dict Settings [readonly]
> +
> +			Holds all the IP network settings.
> +
> +			string Interface [readonly, optional]
> +
> +				Holds the interface of the network interface
> +				used by this connection (e.g. "ppp0" "usb0")
> +
> +			string Method [readonly, optional]
> +
> +				Holds the IP network config method.
> +					"static"- Set IP network statically
> +					"dhcp"  - Set IP network through DHCP

Actually you should remove this, there is no dhcp configuration with
PPP; it will always be static.

> +
> +			string Address [readonly, optional]
> +
> +				Holds the IP address for this connection.
> +
> +			string Netmask [readonly, optional]
> +
> +				Holds the Netmask for this connection.

Likely this will always be the same value (e.g. point to point netmask).
 Whether you want to still include this is up to you.

> +
> +			array{string} DomainNameServers [readonly, optional]
> +
> +				Holds the list of domain name servers for this
> +				connection.

The obvious part that is missing is the dial string, but I guess you are
leaving it out on purpose for now...

Regards,
-Denis

  reply	other threads:[~2011-12-15  1:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 14:59 [RFC v3 00/16] Add DUN support Daniel Wagner
2011-12-13 14:59 ` [RFC v3 01/16] elect: Add skeleton implementation Daniel Wagner
2011-12-13 14:59 ` [RFC v3 02/16] elect: Add D-Bus error messages Daniel Wagner
2011-12-13 14:59 ` [RFC v3 03/16] elect: Add D-Bus configuration file Daniel Wagner
2011-12-13 14:59 ` [RFC v3 04/16] elect: Add systemd " Daniel Wagner
2011-12-13 14:59 ` [RFC v3 05/16] elect: Add Manager interface Daniel Wagner
2011-12-13 15:00 ` [RFC v3 06/16] elect: Add skeleton implementation for device Daniel Wagner
2011-12-13 15:00 ` [RFC v3 07/16] elect: Manager append devices Daniel Wagner
2011-12-13 15:00 ` [RFC v3 08/16] bluetooth: Add Serial interface definition Daniel Wagner
2011-12-13 15:00 ` [RFC v3 09/16] elect: Add BlueZ hooks to device Daniel Wagner
2011-12-13 15:00 ` [RFC v3 10/16] elect: Add device D-Bus interface Daniel Wagner
2011-12-13 15:00 ` [RFC v3 11/16] elect: Dis/Connect Serial interface Daniel Wagner
2011-12-15  0:56   ` Denis Kenzior
2011-12-13 15:00 ` [RFC v3 12/16] elect: Add skeleton dial implementation Daniel Wagner
2011-12-15  1:15   ` Denis Kenzior
2011-12-13 15:00 ` [RFC v3 13/16] elect: Add ppp callbacks to device Daniel Wagner
2011-12-13 15:00 ` [RFC v3 14/16] elect: Add GatChat and PPP handler Daniel Wagner
2011-12-15  1:20   ` Denis Kenzior
2011-12-13 15:00 ` [RFC v3 15/16] elect: Add test scripts Daniel Wagner
2011-12-13 15:00 ` [RFC v3 16/16] elect: Add documentation Daniel Wagner
2011-12-15  1:10   ` Denis Kenzior [this message]
2011-12-16  8:44     ` Daniel Wagner
2011-12-16  9:40       ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EE9491F.50709@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox