mardi 10 avril 2007
Migration : done !
Par Alain Saint-Etienne, mardi 10 avril 2007 à 11:18 :: Méta :: DNS homenet ouvaton
La migration est finie, les commentaires sont à nouveau activés.
vendredi 30 mars 2007
Méfiez-vous des systèmes anti-spam !
Par Alain Saint-Etienne, vendredi 30 mars 2007 à 21:41 :: Commenté ailleurs :: DNS e-mail internet security spam
C'est en tout cas l'opinion que j'ai exprimée, le coude sur le zinc, au bar de Gandi.
lundi 12 mars 2007
Migration time (again)
Par Alain Saint-Etienne, lundi 12 mars 2007 à 23:55 :: Méta :: DNS homenet ouvaton
Diverses migrations à venir (DNS, hébergement) m'obligent à vous interdire temporairement commentaires et trackbacks.
Mais c'est pour la bonne cause : vous ne comprendriez pas que je vous dise "désolé, votre commentaire est arrivé après le transfert de la base", ou encore plus abscons "oui, vous avez cru que votre commentaire avait été enregistré, mais votre cache DNS pointait vers l'ancien serveur..." et touti quantim.
Bref, le site devient statique jusqu'à la fin de la migration.
Pour votre bien !
...et le mien ;-)
mardi 30 mai 2006
Why should I care about domain names and DNS ?
Par Alain Saint-Etienne, mardi 30 mai 2006 à 00:00 :: General :: AJAX cookies DNS javascript stupid men web
Though I had always known this for having been told it by someone I trusted (and of course having experienced it more than once), I had never found, until today, anything on the web describing the "JavaScript Security: Same Origin" policy.
If you (still) don't know nothing about this, can influence the decision (you should want to) and are interested in knowing why you had better be using a safe, future-proof domain naming pattern like :
www.myorganization.tld
services.myorganization.tld
hypeproduct.myorganization.tld
..rather than a whistling, MBA-oriented scheme like :
www.myorganization.tld
www.myorganization-services.tld
www.tophypeproduct.tld
... then you should read the aforementioned page, brought to you courtesy of the Mozilla foundation.
...and try javascripting or use cookies across MBA-named domains to figure out what you can't do if you don't get your point heard and acknowledged.
The definite practical, best-of breeds (both acceptable by MBA's and technically sound) solution still being having www.eyecandy.tld (the URL you put on prints, and waste your marketing budget on) silently redirect to whateverserver.mycompany.tld
Still need an argument when "not being javascript-safe" or "being cokie-unfriendy" sounds too darn dont-bore-me-with-technical-stuff-just-get-us-rid-of-them to the decision-maker you're dealing with ?
Once in you life, let the hype be your friend, and enjoy : let him know he can't do AJAX without.
Problem solved ;-)
Thanks g(2.)0d
If you (still) don't know nothing about this, can influence the decision (you should want to) and are interested in knowing why you had better be using a safe, future-proof domain naming pattern like :
www.myorganization.tld
services.myorganization.tld
hypeproduct.myorganization.tld
..rather than a whistling, MBA-oriented scheme like :
www.myorganization.tld
www.myorganization-services.tld
www.tophypeproduct.tld
... then you should read the aforementioned page, brought to you courtesy of the Mozilla foundation.
...and try javascripting or use cookies across MBA-named domains to figure out what you can't do if you don't get your point heard and acknowledged.
The definite practical, best-of breeds (both acceptable by MBA's and technically sound) solution still being having www.eyecandy.tld (the URL you put on prints, and waste your marketing budget on) silently redirect to whateverserver.mycompany.tld
Still need an argument when "not being javascript-safe" or "being cokie-unfriendy" sounds too darn dont-bore-me-with-technical-stuff-just-get-us-rid-of-them to the decision-maker you're dealing with ?
Once in you life, let the hype be your friend, and enjoy : let him know he can't do AJAX without.
Problem solved ;-)
Thanks g(2.)0d