FilesExpand file tree

development

/

transport.h

Copy path

Blame

More file actions

Blame

More file actions

Latest commit

 

History

History

History

105 lines (98 loc) · 3.07 KB

development

/

transport.h

Copy path

Top

File metadata and controls

• Code
• Blame

105 lines (98 loc) · 3.07 KB

Raw

Copy raw file

Download raw file

Open symbols panel

Edit and raw actions

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

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

96

97

98

99

100

101

102

103

104

105

/*

* Copyright (C) 2009-2011 the libgit2 contributors

*

* This file is part of libgit2, distributed under the GNU GPL v2 with

* a Linking Exception. For full terms see the included COPYING file.

*/

#ifndef INCLUDE_transport_h__

#define INCLUDE_transport_h__

#include "git2/transport.h"

#include "git2/net.h"

#include "vector.h"

#define GIT_CAP_OFS_DELTA "ofs-delta"

typedef struct git_transport_caps {

int common:1,

ofs_delta:1;

} git_transport_caps;

/*

* A day in the life of a network operation

* ========================================

*

* The library gets told to ls-remote/push/fetch on/to/from some

* remote. We look at the URL of the remote and fill the function

* table with whatever is appropriate (the remote may be git over git,

* ssh or http(s). It may even be an hg or svn repository, the library

* at this level doesn't care, it just calls the helpers.

*

* The first call is to ->connect() which connects to the remote,

* making use of the direction if necessary. This function must also

* store the remote heads and any other information it needs.

*

* The next useful step is to call ->ls() to get the list of

* references available to the remote. These references may have been

* collected on connect, or we may build them now. For ls-remote,

* nothing else is needed other than closing the connection.

* Otherwise, the higher leves decide which objects we want to

* have. ->send_have() is used to tell the other end what we have. If

* we do need to download a pack, ->download_pack() is called.

*

* When we're done, we call ->close() to close the

* connection. ->free() takes care of freeing all the resources.

*/

struct git_transport {

/**

* Where the repo lives

*/

char *url;

/**

* Whether we want to push or fetch

*/

int direction : 1, /* 0 fetch, 1 push */

connected : 1;

/**

* Connect and store the remote heads

*/

int (*connect)(struct git_transport *transport, int dir);

/**

* Give a list of references, useful for ls-remote

*/

int (*ls)(struct git_transport *transport, git_headarray *headarray);

/**

* Push the changes over

*/

int (*push)(struct git_transport *transport);

/**

* Send a 'done' message

*/

int (*send_done)(struct git_transport *transport);

/**

* Negotiate the minimal amount of objects that need to be

* retrieved

*/

int (*negotiate_fetch)(struct git_transport *transport, git_repository *repo, git_headarray *list);

/**

* Send a flush

*/

int (*send_flush)(struct git_transport *transport);

/**

* Download the packfile

*/

int (*download_pack)(char **out, struct git_transport *transport, git_repository *repo);

/**

* Fetch the changes

*/

int (*fetch)(struct git_transport *transport);

/**

* Close the connection

*/

int (*close)(struct git_transport *transport);

/**

* Free the associated resources

*/

void (*free)(struct git_transport *transport);

};

int git_transport_local(struct git_transport **transport);

int git_transport_git(struct git_transport **transport);

int git_transport_http(struct git_transport **transport);

int git_transport_dummy(struct git_transport **transport);

#endif