jasder
/
runc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Use conventional factory terminology 

The Initialize method is responsible for creating a new Container instance
and calling it Create makes the factory pattern more obvious. Clearly
creating a Container instance involves initialising the instance.

Docker-DCO-1.1-Signed-off-by: Glyn Normington <gnormington@gopivotal.com> (github: glyn)
This commit is contained in:
Glyn Normington 2014-07-10 11:50:51 +01:00
parent ca2de1bc2c
commit b42d0cb1da
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
factory.go
View File

@ -1,7 +1,7 @@
package libcontainer
type Factory interface {
// Initializes a new container in the given path. A unique ID is generated for the container and
// Creates a new container in the given path. A unique ID is generated for the container and
// starts the initial process inside the container.
//
// Returns the new container with a running process.
@ -12,7 +12,7 @@ type Factory interface {
// System error
//
// On error, any partially created container parts are cleaned up (the operation is atomic).
Initialize(path string, config *Config) (Container, error)
Create(path string, config *Config) (Container, error)
// Load takes the path for an existing container and reconstructs the container
// from the state.