Alfred Gilmore
Alfred Gilmore (June 9, 1812 – June 29, 1890) was a Democratic member of the U.S. House of Representatives from Pennsylvania.
Alfred Gilmore | |
|---|---|
| Member of the U.S. House of Representatives from Pennsylvania's 24th district | |
| In office March 4, 1849 – March 3, 1853 | |
| Preceded by | Alexander Irvin |
| Succeeded by | Carlton B. Curtis |
| Personal details | |
| Born | June 9, 1812 Butler, Pennsylvania |
| Died | June 29, 1890 (aged 78) New York City, New York |
| Political party | Democratic |
| Alma mater | Washington College |
Biography
Alfred Gilmore (son of John Gilmore) was born in Butler, Pennsylvania. He was graduated from Washington College in Washington, Pennsylvania, in 1833. He studied law, was admitted to the bar in 1836 and commenced practice in Butler.
Gilmore was elected as a Democrat to the Thirty-first and Thirty-second Congresses. He was not a candidate for reelection in 1852. He resumed the practice of law in Philadelphia, and later moved to Lenox, Massachusetts, in 1866, and continued the practice of his profession. He died while on a visit in New York City in 1890. Interment in Lenox Cemetery in Lenox, Massachusetts.
Sources
- United States Congress. "Alfred Gilmore (id: G000220)". Biographical Directory of the United States Congress.
- The Political Graveyard
| U.S. House of Representatives | ||
|---|---|---|
| Preceded by Alexander Irvin |
Member of the U.S. House of Representatives from Pennsylvania's 24th congressional district 1849–1853 |
Succeeded by Carlton B. Curtis |
Authority control  |
|---|
gollark: Thus bad.
gollark: It does NOT allow random access.
gollark: Hmm, so, designoidal idea:- files have the following metadata: filename, last modified time, maybe permissions (I may not actually need this), size, checksum, flags (in case I need this later; probably just compression format?)- each version of a file in an archive has this metadata in front of it- when all the files in some set of data are archived, a header gets written to the end with all the file metadata plus positions- when backup is rerun, the system™️ just checks the last modified time of everything and sees if its local copies are newer, and if so appends them to the end; when it is done a new header is added containing all the files- when a backup needs to be extracted, it just reads the end, finds the latest versions and decompresses stuff at the right offsetThere are some important considerations here: it should be able to deal with damaged/partial files, encryption would be nice to have (it would probably work to just run it through authenticated AES-whatever when writing), adding new files shouldn't require tons of seeking, and it might be necessary to store backups on FAT32 disks so maybe it needs to be able of using multiple files somehow.
gollark: I have been pondering an osmarksarchiveformat™ because I dislike the existing ones somewhat. Specifically for backups and append-only-ish access. Thusly, thoughts on the design (crossposted from old esolangs)?
gollark: If you run too much current through beans they may vaporise/burn/etc.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.