Not saying technically it's not possible... just other fish to fry for a mostly working (albeit, at times inconvenient) system.
Charles Daminato OpenSRS Product Manager Tucows Inc. - [EMAIL PROTECTED] > -----Original Message----- > From: David Harris [mailto:[EMAIL PROTECTED]] > Sent: October 18, 2001 1:16 PM > To: Charles Daminato; [EMAIL PROTECTED] > Subject: RE: Transfer confirmation "password" terminology is confusing > > > > Charles Daminato wrote: > > We tried links before, but unfortunately certain clients *cough* AOL > > *cough* would break the link at a line break and we had to split the > > variables away from the link ... > > I think a year or so ago I wrote about making the link shorter by packing > the information more smartly into less characters. You were trying to make > URLs like this work: > > https://rr-n1-tor.opensrs.net/transfers/index.cgi?rid=318&bt=1&ord > num=42693& > password=wsdN4tjNfK > > No wonder it wrapped! > > Consider writing your URL this way: > > https://xfer.opensrs.net/42693/wsdN4tjNfK > > This is only 41 characters long. No need to encode the info using GET form > notation, when you can simply encode the data in PATH info. And no need to > include the reseller id, because you can look that up from the > order number. > > This is already shorter than the 57 character URL > "https://rr-n1-tor.opensrs.net/transfers/index.cgi?rid=318"; that you are > publishing now!!!! I can't imagine any mail client wrapping it. > > You could also squeeze an extra few characters out by removing the second > slash and encoding the number in URL-modified base64. Each digit in a base > 10 number only takes 0.55 digits in base 64! So, we could squeeze > out three > characters and have: > > https://xfer.opensrs.net/Q8JwsdN4tjNfK > > Then, if you care to use a shorter domain name, you can get: > > https://osrs.net/Q8JwsdN4tjNfK > > Only 30 characters long! > > Don't tell me this is not technically possible. Have your technical people > put on their outside-the-box thinking caps. :-) > > David > > >
