On Aug 25, 2008, at 10:02 AM, Sterling Hanenkamp wrote:
On Mon, Aug 25, 2008 at 8:00 AM, Jesse Vincent <[EMAIL PROTECTED]
> wrote:
Sterling,
My cranky-architect comments are that the name "metadata" isn't really
very evocative and that without docs or tests, the patch isn't likely
to be used by many people and is likely to get broken the first time
someone tries to clean up one of these codepaths.
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.
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:
That all sounds pretty reasonable.
-j
framework:
javascript:
ajax_update_class: MyApp.AjaxUpdate
pubsub_update_class: MyApp.PubSubUpdate
to make all the event handler code use a custom class instead. Just
thinking out loud...
Cheers,
Sterling
In general, though, I'm a fan. I know that we've had code that does
something along these lines before, though I don't recall the exact
mechanism. Similarly, alex has been doing a lot of work on the pubsub
stuff and I know it's possible for the server to build up and stream a
queue of fragment updates for the client side. It'd be cool if there
were more unity between these mechanisms.
-j
_______________________________________________
jifty-devel mailing list
jifty-devel@lists.jifty.org
http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
_______________________________________________
jifty-devel mailing list
jifty-devel@lists.jifty.org
http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
_______________________________________________
jifty-devel mailing list
jifty-devel@lists.jifty.org
http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
