Complete.Org: Mailing Lists: Archives: gopher: July 2009:
[gopher] Re: Writing a gopherd for Fellig.org: menu size
Home

[gopher] Re: Writing a gopherd for Fellig.org: menu size

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Writing a gopherd for Fellig.org: menu size
From: Philipp Schafft <lion@xxxxxxxxxxxxxxx>
Date: Thu, 23 Jul 2009 15:06:44 +0200
Reply-to: gopher@xxxxxxxxxxxx

reflum,
On Thu, 2009-07-23 at 05:27 -0700, Cameron Kaiser wrote:
> > flum,
> > I'm currently writing a gopherd for Fellig.org.
> > It needs to handle a lot of 'files' (most of the data is in a DB).
> > 
> > I asked my self for a good maximum size for menus.
> > How many documents/dirs/links/... should I include per menu?
> > 
> > should I use sub'directorys' like this: /foo/d/de/dea/deadbeef.bar
> > or is there something better?
> > 
> > (I will post the link to it as soon as it become productive)
> 
> I'm not sure if you're asking selector length or display string length.
> Selector length is essentially unlimited by the spec, although URL
> pressures tend to keep it under 1K. However, the UMN gopherd client will
> elide display strings longer than 66 characters or so.

I ask about the nummber of entrys. not the length of the entrys
(selector, display strings,...)

-- 
Philipp.
 (Rah of PH2)

-- Attached file included as plaintext by Ecartis --
-- File: signature.asc
-- Desc: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Comment: Because it's your freedom

iQEVAwUASmhgY+uce9VmsoUgAQLjWwf/ZdROaN3noXUyuZrArFkrEhUXCqawR+Ub
KJgW9BiHKJdzlyG5KjBIEJwYsPdm2uXX5K+ocZf8IedJQc/K9qrGnvSr7/f+/Vl8
1GvpkTx7tXR6OpbbnHSa5o6vQ6q9LtIompl4THUiBb8f1CnQO5EtkAUw3mY5i9O7
VgxReilKJksQZjI6zJt75NaFa5c/T/jpysQc1jDpCKmKqO8Fmp3C3+RICy4ef4z9
pLunfrdH0Xouao7w7tO2xUuGFMaFnj+Ad32/IW+6DJyD7VTr0YRoWj1t4fMb98gV
II/DphxtHMMUse8mTzyvPLeZ3/KbhnVRvZwVETkLCg2eShLgu5pCSA==
=Ra17
-----END PGP SIGNATURE-----




[Prev in Thread] Current Thread [Next in Thread]