Skip to content

Documentation updates #27

@sequoiap

Description

@sequoiap

A few things that need to be documented:

  1. Note how user drivers can be used with PyroLab without being added to the library itself; as long as Python can find the module within its environment, and it inherits from the appropriate PyroLab objects, it can be hosted by the daemon.
  2. Create an example of a simple server that just provides a couple of sample services.
  3. A simple nameserver example, include autoclean functionality.
  4. Examples of how to setup and use lockable services.
  5. How autoconnect works.
  6. Configuration files for autolaunching services.
  7. How to implement your own driver, how to contribute it to PyroLab.
  8. When writing autoconnect, account for the fact that other devices may have already connected and PyroLab doesn't need to reconnect to the hardware. If already open, continue using the same connection.
  9. If external connections are failing, is your service being hosted on "localhost" or on "public"?
  10. Note that all attributes on Pyro-compatible objects should be implemented as properties in order to be accessed remotely.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions