upstream/mercurial-mirror Files · hgext/infinitepush/schema.sql

wireprotov2: client support for following content redirects...

wireprotov2: client support for following content redirects And with the server actually sending content redirects, it is finally time to implement client support for following them! When a redirect response is seen, we wait until all data for that request has been received (it should be nearly immediate since no data is expected to follow the redirect message). Then we use a URL opener to make a request. We stuff that response into the client handler and construct a new response object to track it. When readdata() is called for servicing requests, we attempt to read data from the first redirected response. During data reading, data is processed similarly to as if it came from a frame payload. The existing test for the functionality demonstrates the client transparently following the redirect and obtaining the command response data from an alternate URL! There is still plenty of work to do here, including shoring up testing. I'm not convinced things will work in the presence of multiple redirect responses. And we don't yet implement support for integrity verification or configuring server certificates to validate the connection. But it's a start. And it should enable us to start experimenting with "real" caches. Differential Revision: https://phab.mercurial-scm.org/D4778

Pulkit Goyal - - Load All Authors

File last commit:

r37204:03ff17a4 default


                r40062:7e807b8a

default

Download file

             schema.sql
        
                    33 lines
            
             | 1.1 KiB
            
                | text/x-sql
            
             |
                TransactSqlLexer
            
             / hgext / infinitepush / schema.sql
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        Pulkit Goyal
    
infinitepush: move the extension to core from fb-hgext...

              r37204
            
      CREATE TABLE `bookmarkstonode` (

        `node` varbinary(64) NOT NULL,

        `bookmark` varbinary(512) NOT NULL,

        `reponame` varbinary(255) NOT NULL,

        PRIMARY KEY (`reponame`,`bookmark`)

      ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

      CREATE TABLE `bundles` (

        `bundle` varbinary(512) NOT NULL,

        `reponame` varbinary(255) NOT NULL,

        PRIMARY KEY (`bundle`,`reponame`)

      ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

      CREATE TABLE `nodestobundle` (

        `node` varbinary(64) NOT NULL,

        `bundle` varbinary(512) NOT NULL,

        `reponame` varbinary(255) NOT NULL,

        PRIMARY KEY (`node`,`reponame`)

      ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

      CREATE TABLE `nodesmetadata` (

        `node` varbinary(64) NOT NULL,

        `message` mediumblob NOT NULL,

        `p1` varbinary(64) NOT NULL,

        `p2` varbinary(64) DEFAULT NULL,

        `author` varbinary(255) NOT NULL,

        `committer` varbinary(255) DEFAULT NULL,

        `author_date` bigint(20) NOT NULL,

        `committer_date` bigint(20) DEFAULT NULL,

        `reponame` varbinary(255) NOT NULL,

        `optional_json_metadata` mediumblob,

        PRIMARY KEY (`reponame`,`node`)

      ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

Pulkit Goyal infinitepush: move the extension to core from fb-hgext...	r37204	CREATE TABLE `bookmarkstonode` (
		`node` varbinary(64) NOT NULL,
		`bookmark` varbinary(512) NOT NULL,
		`reponame` varbinary(255) NOT NULL,
		PRIMARY KEY (`reponame`,`bookmark`)
		) ENGINE=InnoDB DEFAULT CHARSET=utf8;

		CREATE TABLE `bundles` (
		`bundle` varbinary(512) NOT NULL,
		`reponame` varbinary(255) NOT NULL,
		PRIMARY KEY (`bundle`,`reponame`)
		) ENGINE=InnoDB DEFAULT CHARSET=utf8;

		CREATE TABLE `nodestobundle` (
		`node` varbinary(64) NOT NULL,
		`bundle` varbinary(512) NOT NULL,
		`reponame` varbinary(255) NOT NULL,
		PRIMARY KEY (`node`,`reponame`)
		) ENGINE=InnoDB DEFAULT CHARSET=utf8;

		CREATE TABLE `nodesmetadata` (
		`node` varbinary(64) NOT NULL,
		`message` mediumblob NOT NULL,
		`p1` varbinary(64) NOT NULL,
		`p2` varbinary(64) DEFAULT NULL,
		`author` varbinary(255) NOT NULL,
		`committer` varbinary(255) DEFAULT NULL,
		`author_date` bigint(20) NOT NULL,
		`committer_date` bigint(20) DEFAULT NULL,
		`reponame` varbinary(255) NOT NULL,
		`optional_json_metadata` mediumblob,
		PRIMARY KEY (`reponame`,`node`)
		) ENGINE=InnoDB DEFAULT CHARSET=utf8;