http://cutesoft.net/forums/19/ShowForum.aspxenCommunityServer 2.1 SP3 (Build: 20423.1)http://cutesoft.net/forums/thread/69550.aspxMon, 15 Aug 2011 11:16:29 GMT9a74aede-84de-42da-8122-3d80bfaac2cf:69550Upton0http://cutesoft.net/forums/thread/69550.aspxhttp://cutesoft.net/forums/commentrss.aspx?SectionID=19&PostID=69550Thanks, yes, that answers it all nicely.http://cutesoft.net/forums/thread/69545.aspxMon, 15 Aug 2011 02:11:01 GMT9a74aede-84de-42da-8122-3d80bfaac2cf:69545Adam0http://cutesoft.net/forums/thread/69545.aspxhttp://cutesoft.net/forums/commentrss.aspx?SectionID=19&PostID=69545<div>If you access the control using http://localhost, or the IP address of the machine is 127.0.0.1, it will be considered as work station.</div><div>&nbsp;</div><div>The work station doesn't need an extra license file.</div><div>&nbsp;</div><div>Hope it helps.</div><div>&nbsp;</div><div>Keep me posted&nbsp;</div>http://cutesoft.net/forums/thread/69497.aspxThu, 11 Aug 2011 11:17:20 GMT9a74aede-84de-42da-8122-3d80bfaac2cf:69497Upton0http://cutesoft.net/forums/thread/69497.aspxhttp://cutesoft.net/forums/commentrss.aspx?SectionID=19&PostID=69497<div>Could you clarify the following paragraph, please?</div><div>&nbsp;</div><blockquote class="webkit-indent-blockquote" style="margin:0 0 0 40px;border:none;padding:0px;"><div><span class="Apple-style-span" style="color:#000000;font-family:Arial, Verdana, Helvetica, sans-serif;"><em>You may also install and use the Software on an unlimited number of developer workstations (but not on a development server) for use in connection with the same single website host name when accessed by the<span style="color:#224488;">http://localhost/Webapplication </span></em></span></div></blockquote><div>&nbsp;</div><div>The most confusing part of this text is "for use in connection with the same single website host name," which seems to impose a specific restriction and yet to have no specific technical or legal meaning.</div><div>&nbsp;</div><div>Here are some scenarios that appear reasonable, so I'll ask if these fit the definition of permitted developer workstations:</div><div>&nbsp;</div><div><ul><li>Any computer running the code through loopback / 127.0.0.1 / localhost, when that computer is not the same box as the licensed production server. &nbsp;(The quoted text almost sounds like a "developer workstation" is intended to be a terminal application running locally against the production server.)<br />&nbsp;</li><li>The localhost URL root corresponds to the production server URL root. &nbsp;That is to say, the local copy of http://www.mysite.com/abc/page.php is located at http://localhost/abc/page.php, NOT at http://localhost/mysite/abc/def.php. &nbsp;No particular directory name is required on localhost, no "umbrella" directory is required locally, and there is no requirement preventing any pages using Cute Editor from being at the localhost URL root, e.g. http://localhost/page.php.<br /><br /></li><li>The virtual site using Cute Editor can be identified locally as something like http://mysite.localhost/... or as http://mylocalsite/... or as http://127.0.0.1/... or any other locally defined name running on loopback, so that various distinct applications under development do not collide on localhost/</li></ul></div><div>&nbsp;</div><div>Are there licensing-related technical characteristics that will cause any of these scenarios to fail? &nbsp;For instance, must a developer use exactly http://localhost/... and reconfigure its Apache DocumentRoot whenever switching from one test/development code base to another?</div><div>&nbsp;</div><div>Is it accurate to say that in your language, the difference between a developer workstation and a development server is only that a development server accepts remote connections?</div><div>&nbsp;</div><div>Thanks...&nbsp;</div>