OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wemi message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wemi] Context thoughts


Hi Serge!

My bad - everyone with link can write in this document now :-)
Feel free to modify the doc directly!

Vennlig hilsen/Best regards
Enonic AS

Thomas Sigdestad
CTO
+47 98236011

An Open Source Company


From: "Serge Huber" <shuber@jahia.com>
To: "Thomas Lund Sigdestad" <tsi@enonic.com>
Cc: "wemi" <wemi@lists.oasis-open.org>
Sent: Thursday, February 14, 2013 8:50:53 AM
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!

Here's a link to my document where I try to explain some of my thoughts related to context.. Also the ideas from Alex' document should be included! I've had too little time to work on this as we've moved offices since our last meeting!

I am more than willing to enrich this further - preferably in some kind of workshop with some of you? Boris, Alex?

https://docs.google.com/document/d/1t4_OQOE3OUbW_85gR_1-JgV9XrSNRL0SCVlzSk_L8EA/edit?usp=sharing

An observation: - this is something that just about every web-developer in the world could make real use of :-)


Vennlig hilsen/Best regards
Enonic AS

Thomas Sigdestad
CTO
+47 98236011

An Open Source Company


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]