Diffa Diffa → 0.8

Comments and changes to this ticket

• You flagged this item as spam.
  

  Jonathan Lister October 8th, 2010 @ 11:02 AM

  • State changed from “new” to “open”
  • Assigned user changed from “Jonathan Lister” to “Ben Hood”
  • Milestone order changed from “35” to “0”

  If the URL of the participants is on another domain (or port), the participants will need to support JSONP for getting the content.

  I have the interface doing what it can to get the content, but it can't access cross-domain stuff.

• 

  Ben Hood October 8th, 2010 @ 11:11 AM

  • no changes were found...
• 

  Ben Hood October 8th, 2010 @ 11:14 AM

  Sorry, I don't understand this: ATM the agent is proxying the call to the participants so I don't see the x-domain implication. BTW this is already working (i.e. the diagnostic box is correctly populated with the content that the demo participant set) for me, so I am a bit confused.

• 

  Ben Hood October 8th, 2010 @ 06:30 PM

  • Assigned user changed from “Ben Hood” to “Jonathan Lister”

  Jonathan, I'm assigning this back to you to denote the fact that next question is for you :-)

• You flagged this item as spam.
  

  Jonathan Lister October 8th, 2010 @ 07:09 PM

  • Assigned user changed from “Jonathan Lister” to “Ben Hood”

  I might be getting the URL for the content-getting from the wrong place, but I think it is from /config/pairs/${id}.

  In this picture, you see the upstream and downstream 'url' parameters pointing to hosts that are on a different port to the agent: http://img.skitch.com/20101008-bja4h8j16at83fpg4xce6bppfg.jpg

  You said it was working for you, so I'm a bit unsure how your browser is doing the x-domain thing.

• 

  Ben Hood October 8th, 2010 @ 10:55 PM

  • Assigned user changed from “Ben Hood” to “Jonathan Lister”

  The call to get the content detail is this one:

  http://diffa.lshift.net/doc/rest/diffs/get/events/p_sessionId/p_evt...

  The UI does a GET on the agent, who, in turn, proxies the actual request out to the individual participants. This is completely transparent to the client, so there is no x-domain issue. Please get in contact with me tomorrow to clarify this because I can see us misunderstanding each via Lighthouse.

• You flagged this item as spam.
  

  Jonathan Lister October 9th, 2010 @ 02:59 PM

  I see! I was using the wrong URL... thanks.

• You flagged this item as spam.
  

  Jonathan Lister October 9th, 2010 @ 03:28 PM

  • Assigned user changed from “Jonathan Lister” to “Ben Hood”

  I have noticed that the response from the server is only "Expanded Detail" - this should send something for each of the upstream and downstream participants. How about:

  {"upstream":"Expanded Detail for upstream","downstream":"Expanded Detail for downstream"}
  

• 

  Ben Hood October 9th, 2010 @ 03:29 PM

  (from [e09b4bbdc1426bf59ee2ca3119b5ce1ae4a35d24]) Getting content from server rather than trying cross-domain requests to participants

  [[#100]] http://github.com/lshift/diffa/commit/e09b4bbdc1426bf59ee2ca3119b5c...

• 

  Ben Hood October 11th, 2010 @ 11:02 AM

  • State changed from “open” to “closed”

  Yes, you're right - ATM the server is only returning a hard coded string "Expanded detail" (see ticket #6 for background). So the call you are currently making is correct, hence this issue can be closed. For note, please see ticket #127 which is related to this issue.

• 

  Ben Hood October 11th, 2010 @ 02:34 PM

  Jonathan - I've plumbed through a little of #6 so that the upstream is being set correctly (i.e. dynamically), but the UI seems to be sending the same for the downstream as well - note that I haven't looked into this in detail yet. Do you have any ideas off the top of your head?

• You flagged this item as spam.
  

  Jonathan Lister October 11th, 2010 @ 03:39 PM

  As you've pointed out, the interface needs to discriminate between the two participants. I'll make the future notes on #6.