The server MAY implement denial-of-service safety limiting the number fetches for a spec in a given time period, as a courtesy to builders. The server SHOULD honor an IgnoreCache processing option. This causes all built-in spec caches to be ignored, fetching the spec immediately from its canonical useful resource. This feature is very helpful while developing a gadget. HTTP-primarily based request servers SHOULD assist this through a URL parameter named nocache.
Gadget servers should assist as many options as possible. Widely used, highly really helpful options are listed on the end of this document. Multiple Content sections could also be specified in gadget XML. Each is labeled with a number of optional view identifiers, which allow the gadget to behave or seem in another way relying on the context in which it is rendered. These are key/worth pairs that kind the basis of gadget configuration and persistence. They are most often manipulable by users of the gadget, and are continued on behalf of a consumer in order that the gadget has entry to them across multiple rendering requests. The gadget container is typically answerable for offering their persistence for this information and an interface to edit it.
URL to a Gadget Rendering Request for the requested gadget. Processed gadget content, the results of steps #four and presumably #5. The message MAY provide contact data for the gadget server administrator, along with a mechanism to request adding support for the feature. The XML MUST conform to the extended gadget spec XSD. This XSD represents all legitimate elements and attributes accepted by the legacy iGoogle gadget server (gmodules.com). The canonical gadget spec XSD contains the subset of attributes that must be parsed and interpreted by the server. In different phrases, the parser MUST NOT reject gadget specs conforming to the extended spec, but needn’t interpret greater than the canonical spec.