Hi Rajasekhar.

The most straightforward way to determine the time savings that
Preload tags offer is by firing a request without a Preload tag, then
firing the request after adding the tag. Firebug and similar tools can
measure the duration of time between request and response and you can
compare these figures to see the improvement. Quick note: make sure to
append an arbitrary parameter to your requests to make sure orkut
isn't pulling the response from cache -- this is the only way to
ensure a fair contest. While I don't have any comparisons of my own on
hand, the response from developers who have added Preload tags has
been overwhelmingly positive.

To answer your other questions:
- As far as I know, you can include as many Preload tags as you need.
- If you don't include the 'views' attribute, Preload tags are applied
to both the canvas and profile views.
- If you don't include the 'authz' attribute, requests sent to your
server will not be signed by orkut. All requests that attempt to
access user-specific information stored on your back-end should be
signed to verify their authenticity.

Please let me know if you need any more facts.

Cheers!
- Jason

On May 16, 3:57 am, Rajasekhar <[EMAIL PROTECTED]> wrote:
> Hi Googlers,
>
> when i use the preload
>
> how can i test the performance and how many preloads i can use in my
> xml.
>
> and if not use the view param then is it available in both views ,
> andif not use authz what happen
> and please give me the clear explanation about <preload>
>
> I checked both urls given by 
> arne.http://code.google.com/p/opensocial-resources/wiki/LatencyCombatField...
>
> Thank
> RajaSekhar
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Orkut Developer Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/opensocial-orkut?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to