Hi, this is an nice idea. So we have a possibility to read the ident's.
—— best regards Kris —— Fresh ideas for your business —— D³ Data Development · Stollberger Straße 23 · D-09380 Thalheim Fon 03721 268090 Fax 03721 265234 -------- Original Message -------- Subject: [oxid-dev-general] Using base64 instead of md5 for seo idents? (19-Apr-2013 11:12) From: André Herrmann <[email protected]> To: [email protected] > Hi folks, > > due oxseohistory table is a growing blackbox, wouldn't it make sense to > use base64_encode instead of md5 for generating idents in seo table? > This would make it easy to make historical links visible because there > is a decode function for this. > > In current oxseohistory table, the only possibility to get the former > SEO-Links is to play "man in the middle" and track and store any call > that goes to oxseohistory. > > Would you generally agree with my suggestion to use base64 instead of > md5 for seo idents or do you see any problems here? > > Greetings, > > André > > -- André Gregor-Herrmann > Entwicklung, Administration, Projektmanagement > > mail [ [email protected] ] > > web [ www.fatchip.de ] > > FATCHIP [ GmbH ] | sitz [ Helmholtzstrasse 2-9 | 10587 Berlin ] | fon > [ 030.39 88 93 51 ] | fax [ 030.39 88 93 52 ] | mail [ kontakt@ > fatchip.de ] | Ust-Id. [ DE 265567757 ] | Amtsgericht [ Berlin- > Charlottenburg ] | HRB [120567 B] | Geschäftsführung [ Dipl.-Ing. Hendrik > Bahr ] > > Be Smart, Go Green. Don’t print this email unless you really need to. > > _______________________________________________ > dev-general mailing list > [email protected] > http://dir.gmane.org/gmane.comp.php.oxid.general > _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
