fieldOfView | SPi-V devdomain license and subdomains
I need to buy a domain license for my client, and I wonder what exactly should be entered in the license tool to get widest license possible. I've seen in a previous discussion that a domain is derived if you enter a full path in the tool, but I've found no clear information about what you call a "domain".
Is it only the 2 last dot-separated items from the first "/"-separated item from the url, or is it this whole first item ?
As an example, if XML files are posted within the "domain.com" domain, currently at "http://www.subdomain.domain.com/", what should be entered in the license tool ?
1. "domain.com"
2. "subdomain.domain.com"
3. "www.subdomain.domain.com"
4. "http://www.subdomain.domain.com/"
Will spi-v files work if the url is changed in the future to "http://subdomain.domain.com/" ?
Could some spi-v files be served from another subdomain of the same domain with the same domain license, for instance from "http://another.domain.com/" ?
Thanks for answers,
Best regards,
Re: domain license and subdomains
A new, clearer license tool is undergoing final testing as I type. Well, not as I type, because I can not type and test at the same time, but you understand what I mean ;-)
The domain license is specific to a domain, not to any path information (very early, that used to be different). You must specify the full domain, including subdomains. The only exception is the 'www.' subdomain.
If you enter 'example.com', the domain license will be valid anywhere on 'http://example.com' and 'http://www.example.com', but not on 'http://subdomain.example.com'.
If you have a license for 'http://subdomain.example.com', SPi-V will work in licensed form as long as it thinks that it is served from 'subdomain.example.com'. The HTML file that opens SPi-V.dcr does not have to be on the same domain; you can specify a full URL (including a domain name) in the src param of your object/embed code.
Shockwave files can only open files from the same domain as the Shockwave movie. So you can not have SPi-V.dcr on subdomain.example.com and your panoramas on another.example.com. If both subdomains are on the same server, it should not be too difficult to maskerade the files as served from the other subdomain.
Re: domain license and subdomains
OK, thanks for the clarifications. Just to be sure, if I enter "subdomain.example.com", will it work from http://www.subdomain.example.com ?
Regarding Shockwave security rules, I don't think you're right. I have allready used several times some Shockwave movie posted on subdomain.example.com and they can access any data at another.example.com or anyone.example.com without asking for authorization from the user, wherever there would be a dialog involved if I try to access data outside example.com.
Re: domain license and subdomains
Yas, for SPi-V subdomain.example.com and www.subdomain.example.com are the same domains.
I am not doing anything to further restrict the use of subdomains (other than the subdomain where the SPi-V.dcr movie lives), so if it works in Shockwave, it works in SPi-V.
Spi-V domain license problem
I sent this question by mail to info@fieldofview.nl yesterday but haven't got any answer yet. I'm posting it here as it may interest the whole dev community...
We have just bought a domain license from the license-tool where we have entered "citevisions.rennes.fr" as we have discussed on the forum last week.
It seems it does not prevent the splash screen to appear in the following movie (for instance) :
http://www.citevisions.rennes.fr/citevisions/visite.php?visite=mairie12
although I have put the domain license file at
http://www.citevisions.rennes.fr/citevisions/license.xml
next to the Spi-V.dcr movie...
As each pano are in its own xml file, the splash screen is shown at every jump to a new scene.
Could you help me to solve this issue ?
Re: Spi-V domain license problem
Sorry for the delay. I have sent you a new license.
There's currently a problem with Shareit not registering the info it should get from the license tool. This means licenses that get sent out can be invalid. If this happens, send me an email and I'll get you a working license ASAP.
PS: nice idea with the fading hotspots