[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wemi] Context thoughts
Hello Thomas, A big thanks for putting this together, I think it really helps get the ball rolling. Could you maybe enable comments on the document ? Anyway here are mine directly here : "Technical Request * The context should "piggy-back" every request either as header value(s) or cookie(s)" -> What about request parameters, could we use those too ? "Response * Return updated context to the client" -> How is the response returned ? Is there both content and context ? How are they separated ? Should we use HTTP headers (seemed they were frowned upon by some experts that Cedric consulted), or define a specific part of the JSON data returned ? "Reference Implementations:" -> Thanks for included this part about implementations, I think we need to remember that we should provide at least a minimal set of client and server implementations to make sure it is easy to implement and understand. "What context do we already have from HTTP" -> Actually one of the most used HTTP fields is the referrer field, which helps build browsing context data and analyze browsing patterns. In a more general way, we could also look at existing context providers, mostly publicly available social servers such as Facebook, LinkedIn or others, that could provide context about visitors. Best regards, Serge Huber. - -- --- -----=[ shuber at jahia dot com ]=---- --- -- -
CTO & Co-founder - Jahia Solutions Group, 9 Routes de Jeunes, 1227 Acacias, Switzerland Jahia’s next-generation, open source CMS stems from a widely acknowledged vision of enterprise application convergence – web, search, document, social and portal – unified by the simplicity of web content management. http://www.jahia.com On 13 févr. 2013, at 16:43, Thomas Lund Sigdestad <tsi@enonic.com> wrote: Hi All! |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]