Archontophoenix maxima
Archontophoenix maxima, the Walsh River palm, is the largest species of the genus Archontophoenix. It is endemic to Queensland, Australia. This robust palm grows in rainforest in altitudes of between 800 and 1200 metres on the Walsh River and the adjacent Mount Haig Range in the Atherton Tablelands at approximately 17° South latitude.
| Archontophoenix maxima | |
|---|---|
 | |
Scientific classification  | |
| Kingdom: | Plantae |
| Clade: | Tracheophytes |
| Clade: | Angiosperms |
| Clade: | Monocots |
| Clade: | Commelinids |
| Order: | Arecales |
| Family: | Arecaceae |
| Genus: | Archontophoenix |
| Species: | A. maxima |
| Binomial name | |
| Archontophoenix maxima Dowe | |
Description
Archontophoenix maxima grows up to 25 metres tall, with a trunk up to 30 cm in diameter with an expanded base. The rigidly-held, erect leaves are up to 4 metres long, and have a slight sideways twist. The massive branched inflorescence is up to 1.5 metres long, and bear white flowers. When ripe, the fruit is red and between 13 and 15 mm in length. The flowers closely resemble those of A. alexandrae.
gollark: ... no.
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)?
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.