[Cosmo-dev] replacing json-rpc with atom for preview

Mikeal Rogers mikeal at osafoundation.org
Fri Mar 30 12:09:59 PST 2007


I want to begin by saying I think it's a good idea to get away from  
our current monolithic jsonrpc service. It's fairly ugly and is going  
to get a little unmanageable unless we do something about it and this  
might be a good chance to up our performance.

But, I think it's worth looking at all of our options and even  
looking at not using a standards based solution if it's going to  
increase webui performance.

>> does anybody have any questions or concerns about this proposal?

My main concern is parsing time on the client side javascript.

http://code.google.com/apis/gdata/json.html#Background

If we use json like the examples in the document above which use a  
namespace looking markup, we may end up adding a lot of extra parse  
time.

It's also important to note that although all the gdata feeds at  
google have this option none of the actual google webapps use this  
feature, the actual data format that's sent between the server and  
client js varies a little from app to app but none of them use this,  
or anything that would take this long to parse.

All the performance stuff continues to freak me out the more I think  
about the amount of events we'll be sending if we do either a month  
view or calendar overlays, or god forbid BOTH.

>
> The areas where I would have concerns:
>
> 1. Impact on schedule - I think that a successful prototype would  
> address this concern

I would really like to see some perf numbers for parsing this kind of  
data format from mde as well. Especially if we turn up the number of  
events to 1000+.

> 2. Impact on quality of the Web UI -- having it regress from where  
> it is now would be bad -- I'm not sure that doing Atom is any worse  
> than what we already planned to do for the dashboard, so this isn't  
> really an increase in risk from where we are now.

It could be if we add additional parse time.

>
> Ted
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/cosmo-dev/attachments/20070330/b91c00f3/PGP.pgp


More information about the cosmo-dev mailing list