Will this work with Domain Access module?

I have never used the domain access module. So, no special considerations were taken to ensure this.

Can you give me a use-case as to how you would envision it working?

I have used it. It relies on Drupal's core Node access settings to determine whether or not a user may view content on a given 'domain' (or site, more truthfully). Basically, it allows several Drupal sites to share one database, but separate content access permissions for each site. I haven't much experience with Drupal's Entities, but I assume that since they aren't Nodes, and that since Entity types aren't available as user access permissions on admin/people/permissions page, that Entities will be entirely unavailable to the Domain Access module without some additional functionality. Perhaps the Domain Access issue queue can shed some light on how it might work with Entities. Here is one issue that may be relevant.

I see.

Thanks duntuk. Makes complete sense, However after some review of the domain access module and sifting through their issue queue, i don't foresee them adding in support for entities anytime soon.

All of dRealty's content is implemented as entities and i really don't see a way (or an easy one) to make it work with the domain access module.

Now, having said all that i can see where your use case could be beneficial and/or marketable to more than just yourself, this is a feature that i could see putting into the module, just not sure of the best way to go about it. I'm open to ideas.

BUT, first and foremost on the priority list will be getting a full release candidate completed before the end of the month, so i doubt this is something that is going to get much attention unless it gains more support, gets sponsored, or someone other than myself spearheads the development of that feature set.