Yeah, would be a good idea to add the note. I bet the reason its set up that way is so that people can't snag your library stacks and pick em apart for site hacking purposes. If you hit the url for a .livecode file directly, it only returns the very first string that designates the stackfile format. Nothing else gets sent so they're definitely having something else step in and process those files.
Pretty good idea actually. Otherwise it would make the security benefit of using stack file libraries go poofy. On Thu, May 23, 2013 at 10:50 AM, Robert Mann <r...@free.fr> wrote: > Yeap!! Brilliant!! That is it... the LC server Beast was ruling the file > system behind the scene!! > So I'think it's going to be a good idea for me to go and append the > documentation of "go stack url" for on-rev users and put a warning for the > ones who would try and download a stack from a folder "covered" by LC > server! Thanks a lot for taking a look at that! > > > > > -- > View this message in context: > http://runtime-revolution.278305.n4.nabble.com/start-using-stack-tp4665159p4665307.html > Sent from the Revolution - User mailing list archive at Nabble.com. > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
