<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 25, 2008, at 10:02 AM, Sterling Hanenkamp wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">On Mon, Aug 25, 2008 at 8:00 AM, Jesse Vincent <span dir="ltr"><<a href="mailto:jesse@bestpractical.com">jesse@bestpractical.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Sterling,<br> <br> My cranky-architect comments are that the name "metadata" isn't really<br> very evocative and that without docs or tests, the patch isn't likely<br> to be used by many people and is likely to get broken the first time<br> someone tries to clean up one of these codepaths.</blockquote><div><br>Agreed. Which is why I essentially said not to use the patch in the comments. It's more a proof of concept than a useful hunk of code at this point. However, if there was a mechanism for injecting some information into the returned response that could be reacted to, I think that would be swell. Currently, I'd have to implement such a thing on my own.<br> <br>I'm going to see if I can come up with something that's more flexible and less likely to bring out the cranky-architect. After looking through jifty.js in detail, it looks like Jifty.update() and related functions really ought to be refactored as a Jifty.Update class (probably with a better name than that) with parts that could be used separately and would be more extensible. I could see Ajax and PubSub being extensions of some base with the potential of the application further extending them and then setting:<br> <br></div></div></div></blockquote><div><br></div><div>That all sounds pretty reasonable.</div><div><br></div><div>-j</div><div><br></div><blockquote type="cite"><div dir="ltr"><div class="gmail_quote"><div>framework:<br> javascript:<br> ajax_update_class: MyApp.AjaxUpdate<br> pubsub_update_class: MyApp.PubSubUpdate<br><br>to make all the event handler code use a custom class instead. Just thinking out loud...<br> <br>Cheers,<br>Sterling<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;"><br> <br> In general, though, I'm a fan. I know that we've had code that does<br> something along these lines before, though I don't recall the exact<br> mechanism. Similarly, alex has been doing a lot of work on the pubsub<br> stuff and I know it's possible for the server to build up and stream a<br> queue of fragment updates for the client side. It'd be cool if there<br> were more unity between these mechanisms.<br> <br> -j<br> _______________________________________________<br> jifty-devel mailing list<br> <a href="mailto:jifty-devel@lists.jifty.org">jifty-devel@lists.jifty.org</a><br> <a href="http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel" target="_blank">http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel</a><br> </blockquote></div><br></div> _______________________________________________<br>jifty-devel mailing list<br><a href="mailto:jifty-devel@lists.jifty.org">jifty-devel@lists.jifty.org</a><br>http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel<br></blockquote></div><br></body></html>