Skip to Content.
Sympa Menu

edugain-discuss - Re: [eduGAIN-discuss] Sizes of inline logos in eduGAIN metadata

edugain-discuss AT lists.geant.org

Subject: An open discussion list for topics related to the eduGAIN interfederation service.

List archive

Re: [eduGAIN-discuss] Sizes of inline logos in eduGAIN metadata


Chronological Thread 
  • From: Guy Halse <guy AT tenet.ac.za>
  • To: Stefan Winter <stefan.winter AT restena.lu>, <edugain-discuss AT lists.geant.org>
  • Subject: Re: [eduGAIN-discuss] Sizes of inline logos in eduGAIN metadata
  • Date: Tue, 17 Mar 2020 11:34:31 +0200
  • Organization: Tertiary Education and Research Network of South Africa NPC

Hi

On 2020/03/17 10:48, Stefan Winter wrote:
base64 expresses three binary bytes as four printable characters. There is thus an approximate relation that a base64 string is 4/3 (four thirds) of the binary source. The additional few bytes at the beginning of the URI become less and less significant the bigger the file is.
Sure. My original point was merely that we decide which form makes most sense and be unambiguous :)  I was merely explaining why we use the form we do.

I'm happy to do the maths for my users if the decision is to use the encoded form, and publish a sensible user-understandable limit. Because my experience with email attachments is that even relatively tech savy users don't understand that a 5MB attachment limit means you can only attach a 3.5MB file, and that generates support calls...

-  Guy
--
Guy Halse
Executive Officer: Trust & Identity Tertiary Education & Research Network of South Africa NPC Fault Reporting: +27(21)763-7147 or support AT tenet.ac.za
Office: +27(21)763-7102
http://www.tenet.ac.za/contact
https://orcid.org/0000-0002-9388-8592

PNG image

PNG image

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature




Archive powered by MHonArc 2.6.19.

Top of Page