Batch (obsolete) streams.
It is possible to integrate your listings with a batch flow. However, if you have started from scratch integrating your listings, the real-time, REST approach is strongly recommended.
Batch flows must follow a few rules:
- They must pass validation with the available XSD schema.
- They must be updated and regenerated every 24 hours.
- They must always contain all listings from all integrated agencies.
- Listings not in the feed will be deleted from the portal (the deletion operation is implicit).
- Must not exceed 10,000 listings.
- If you exceed this limit you must implement the REST (real-time) version to integrate your listings
Directions on the use of batch integrations
Pro
- You may have a ready-to-use flow.
- Centralization of the export process.
- Potentially less implementation complexity.
Cons
- Higher processing burden and network traffic.
- No real-time feedback on the outcome of the import.
- Higher latency time between modification on the management system and publication on the portals.
- Waiting time for the actual publication of a listing ranges from one hour to 48 hours.
- A single error in the file can jeopardize the entire flow.
- Increased dependence on support service in case of problems.
The performace of a batch integration cannot be guaranteed. They are in fact conditional.
- by the instant the agency enters or modifies the listing on the management system,
- by the instant and duration of the export process (on the partner's servers),
- by the instant and duration of the import process (on the Real Estate servers).
It is possible to optimize, by agreeing on process scheduling, only the last two steps,
which is why the maximum latency, assuming the best configuration, is still just over 24 h.
/feed
Root node of the XML document.
/feed/properties
Container node of all listing elements.
/feed/properties/property
Container node of the listing to be published or updated.
Each listing is defined with the rules described for REST services.
/feed/auctions
Container node of auction property listings.
/feed/auctions/auction
Container node of the auction to be published or updated.
Each auction is defined with the rules described for REST services.
