A push connection typically connects to the git-receive-pack
service running where the remote repository is stored. This provides a
one-way object transfer service to copy objects from the local repository
into the remote repository, as well as a way to modify the refs stored by the
remote repository.
Instances of a PushConnection must be created by a
org. that implements a specific
object transfer protocol that both sides of the connection understand.
PushConnection instances are not thread safe and may be accessed by only one thread at a time.
Transport
| Modifier and Type | Method and Description |
|---|---|
| public void | push(final ProgressMonitor
progress monitor to update the end-user about the amount of
work completed, or to indicate cancellation. Implementors
should poll the monitor at regular intervals to look for
cancellation requests from the user. monitor, final Map<String, RemoteRefUpdate> map of remote refnames to remote refs update
specifications/statuses. Can't be empty. This indicate what
refs caller want to update on remote side. Only refs updates
with
refUpdates)org.
should passed. Implementation must ensure that and appropriate
status with optional message should be set during call. No
refUpdate with
org.
or
org.
can be leaved by implementation after return from this call.Pushes to the remote repository basing on provided specification. |
| public void | push(final ProgressMonitor
progress monitor to update the end-user about the amount of
work completed, or to indicate cancellation. Implementors
should poll the monitor at regular intervals to look for
cancellation requests from the user. monitor, final Map<String, RemoteRefUpdate> map of remote refnames to remote refs update
specifications/statuses. Can't be empty. This indicate what
refs caller want to update on remote side. Only refs updates
with
refUpdates, OutputStream org.
should passed. Implementation must ensure that and appropriate
status with optional message should be set during call. No
refUpdate with
org.
or
org.
can be leaved by implementation after return from this call.output stream to write sideband messages to out)Pushes to the remote repository basing on provided specification. |
| push | back to summary |
|---|---|
| public void push(final ProgressMonitor monitor, final Map<String, RemoteRefUpdate> refUpdates) throws TransportException Pushes to the remote repository basing on provided specification. This possibly result in update/creation/deletion of refs on remote repository and sending objects that remote repository need to have a consistent objects graph from new refs.
Only one call per connection is allowed. Subsequent calls will result in
Implementation may use local repository to send a minimum set of objects
needed by remote repository in efficient way.
| |
| push | back to summary |
|---|---|
| public void push(final ProgressMonitor monitor, final Map<String, RemoteRefUpdate> refUpdates, OutputStream out) throws TransportException Pushes to the remote repository basing on provided specification. This possibly result in update/creation/deletion of refs on remote repository and sending objects that remote repository need to have a consistent objects graph from new refs.
Only one call per connection is allowed. Subsequent calls will result in
Implementation may use local repository to send a minimum set of objects
needed by remote repository in efficient way.
| |