karl Says:

novembre 28th, 2009 at 10:15

REST est un style architectural qui est encore une couche au dessus de HTTP.

Je rejoins Christian dans son analyse. Chacun des domaines est d’ailleurs interprété en fonction de la culture propre des intervenants. Lorsque l’on SPDY de Google qui est une forme d’extension à HTTP. Ils ne s’intéressent proprement dit qu’à l’efficacité du transport et pratiquement pas à l’amélioration du transfert.

Google centralise tous les services dans une même coquille. Sa seule interaction au final n’est avec qu’avec les logiciels clients. L’interopérabilité avec les autres serveurs n’est presque pas un objectif à terme. Ils ont besoin de rapidité, ils ont des besoins spécifiques qu’ils maîtrisent au cœur de leurs applications. Lorsqu’on a créé un écosystème avec un fort contrôle sur tous les éléments du système, on peut se permettre d’imposer sa loi à l’écosystème. Microsoft l’a fait dans l’univers de la bureautique. Google le fait petit à petit pour le Web. Nous n’y sommes pas encore bien sûr.

Pour Google, le transfert n’est pas important ou plutôt il est si peu mis en pratique (quid de HTTP PUT, DELETE, etc., des mime types et des headers) sur le Web aujourd’hui, que Google peut se concentrer sur ce qui améliore le transport des données.

Browser testing

Work faster. Impress your clients. Test your website designs across all major browsers in seconds with Litmus.

t work we have to manage a ton of Django based sites. Just for our World Company sites, we have over 50 different settings files, and this doesn't take into account the sites that we host for other clients. At this size it becomes basically impossible to test each site in a browser when you push things to production. To solve this problem I have written a very basic server description tool. This allows you to describe sites (settings file, python path, url, etc.) and servers.

15 Questionnaire

It would be very interesting if you could share a mockup, template of your questionnaire. Or if specific to each projects you are creating, at least, the type of questions in the questionnaire.

On the side of the No No for projects, setting a deadline for delivery of the projects or even a step without having all the materials which guarantee the delivery date.

We have to be very careful when committing to dates, to also set the right expectations of the client. Too often, in a project, it is possible to say, let’s release this section at this date YYYY-MM-DD, the materials will be given to you in the next two weeks. Red flag. It is often better to say, once given this list of items (deliveryDate), we will be releasing this section at “deliveryDate 10 business days”.

In middle size agencies, there is also an issue of resources management. There is more than one project in parallel. Explaining to the client that if he/she misses a particular window, the project will be delayed.

Keep written records of every discussions you had, put down the RESOLUTION and the ACTION. After each meeting, send your meeting minutes to the project participants and the client. It is often better to have a scribe. If you get phone calls from the clients (which is fine), send a summary of the discussion just after.

If you are using a project management system (be mail, sharepoint, basecamp, etc. anything), if the client says “It is not the way I work”, rise a red flag again.

Be careful also of the “just this time” or “just for once” on a exceptional work issue, because if you authorize it once, the client will keep the foot in the door, to reuse it again.

posted at 10:38 am on October 21, 2009 by karlcow

A RESTful, hypertext-driven system needs to enable clients to create a new resource that depends on three or more resources of different types. What's the best method to expose this capability?

Tracking your time—for your clients, for yourself—doesn't have to be a dreaded task. Dispense with the preparation, avoidance, and gnashing of teeth. Freckle eliminates all the nonsense between you and your work.