Have a look at it.1. http://aempodcast.com/2015/infrastucture/configure-aem-dispatcher-redirect-based-geolocation/#.WkzfAzfhX4Y 2 .https://dev.maxmind.com/geoip/legacy/mod_geoip2/

Can you explain your use case in more detail. Like what do you mean by "fixed number of assets like 30 at a time"?

Have a look at the sample implementation for this scenario is provide here with Image in core component/apps/core/wcm/components/image/v1/image/clientlibs/editor/js/decorative.click.js-ref to AEM 6.3

Yes, all these are considered "page is changed" but version will only get created when you activate a page after these changes.and you can also create version by yourself https://helpx.adobe.com/experience-manager/6-2/sites/authoring/using/working-with-page-versions.html

With the mentioned article you have already got the path to the image in DAM, you can make a request to that jcr:content of that image to read the properties/metadata and display it any preferred format/UI

You can use code from here to get the current resource name in datasource.http://www.adobeaemclub.com/how-to-fetch-current-resource-path-in-datasource/ Once you have the current resource name, you can reach out to parent and read the properties before creating list

The use case demonstrated is not the production ready version.You can surely make few changes like keeping the config page hierarchy out of project content hierarchy. It will require only minor code change.but it will be available at publish to read configs and in general scenario, page outside proj...

AFAIK, org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl is not a factory configuration but it accepts mapping as multiple properties defined in arrayBut for factory configs like ACS Commons Named Image transformers, having a <unique> identifies holds true

Looks like you are using JSRP (default option with TarMK) which keeps the data only in the instance where it was created.JSRP - https://helpx.adobe.com/experience-manager/6-3/communities/using/jsrp.html

Look at the Reference component mentioned herehttps://helpx.adobe.com/experience-manager/6-3/sites/authoring/using/default-components-foundation.html