<br><br><div class="gmail_quote">2009/5/24 Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div class="im">On Sat, May 23, 2009 at 11:52 PM, Jim Driscoll <span dir="ltr"><<a href="mailto:Jim.Driscoll@sun.com" target="_blank">Jim.Driscoll@sun.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On 5/23/09 10:46 AM, David Geary wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The onevent attribute of <f:ajax> can be used to specify a JS function<br>
to monitor Ajax calls, which is all well and good. However, the data<br>
payload (I'm not sure why we have to refer to it as a payload), seems<br>
strange because:<br>
<br>
1. data.type is always "event". What's the point of that?!?<br>
</blockquote>
<br></div>
Sometimes, it's error. See the jsf-demo/ajax-queue demo for an example that uses this interchangeably.</blockquote></div></div></blockquote><div><br>Okay, that makes sense, I suppose. But the spec, in table 14-4 describes the value of the type parameter as simply "event". That description should be updated.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2. <a href="http://data.name" target="_blank">data.name</a> <<a href="http://data.name" target="_blank">http://data.name</a>> is really the status of the Ajax<div><br>
request. Using "name" for the property seems meaningless. Name of what?</div></blockquote></blockquote></div><div><br><br>Honestly, in looking at the demo you cited, I can't possibly resolve why you would want to use a property called "name". To me, the word "status" wants to come to mind. I really think you could get away with a single property, status.<br>
<br>status could be: begin, complete, success, error<br>Then you have errorCode instead of overloading name. Just get rid of type and name and use status instead.</div></div></blockquote><div><br>Agreed. That was my original objection. "name" implies nothing. Name of what?<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
3. does it make sense to give the page author acdcess to the actual<div><br>
XMLHttpRequest object via the data payload? data.xhr, for example?<br>
</div></blockquote>
<br>
Is your objection that they could modify the object? Since this is JavaScript, they can already modify darn near everything anyway. We could always deliver them a copy of the object, I suppose...</blockquote></div><div>
<br>
I think David is asking whether it is possible to access the object. It appears that data is a copy of the properties from the XHR object, not the object itself. David, do you want the native object?</div></div></blockquote>
<div><br>Yes, I think it'd be useful to provide access to the actual xhr object.<br><br><br>david<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 08ex; padding-left: 1ex;">
<div class="gmail_quote"><div><br><br>-Dan</div></div>
<br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan" target="_blank">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>
</blockquote></div><br>