Re: CFC Addressing
Nope. Each CF instance has a security sandbox which is effectively at runtime. So if the CFCs are accessible, they are governed by the sandbox for the instance that invokes them. On Wednesday, Aug 6, 2003, at 21:58 US/Pacific, Jason Blum wrote: Does anyone happen to know whether one's calling template and one's CFCs can reside in separate security sandboxes? For instance, could an ISP put all client sites in one default security sandbox with few permissions/tags/etc, but then allow them to tie into CFCs in another sandbox that does have all permissions. This would make security, availability and code reuse realitic goals! The obvious answer is to try it. Am struggling with installation problems right now (locked out of CFAdmin by some strange java.lang.NullPointerException) - but saw this discussion and thought I would throw in a related question. Thanks! ~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribeforumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Re: CFC Addressing
On Saturday, Aug 2, 2003, at 05:59 US/Pacific, Jason Blum wrote: Does anyone happen to know whether one's calling template and one's CFCs can reside in separate security sandboxes? For instance, could an ISP put all client sites in one default security sandbox with few permissions/tags/etc, but then allow them to tie into CFCs in another sandbox that does have all permissions. This would make security, availability and code reuse realitic goals! The security system is per instance, i.e., each CFMX instance has its own sandbox security. If you had multiple CFMX (for J2EE) instances on a server, you could define the same shared CFC directory as a custom tag path in each instance and therefore reuse CFCs across multiple instances. However, the security applied would be that for each individual CFMX instance, therefore the same CFCs would be subject to potentially different security rules in each CFMX instance. Sean A Corfield -- http://www.corfield.org/blog/ If you're not annoying somebody, you're not really alive. -- Margaret Atwood ~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribeforumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
RE: CFC Addressing
Hi Sean, Thank you - I see what you mean. Actually the same is true even within a single instance between multiple security sandboxes. It's such a shame because ISP's would benefit so enormously from the ability to not allow clients to query a database (i.e. restricting it in their sandbox) - but allowing them to invoke a CFC in another sandbox that could query that database. Certainly you can do this invoking the CFC as a Web Service. But invoking it without having to run up and down the protocol stack would be awfully nice! Thanks for your thoughts on this... -Jason -Original Message- From: Sean A Corfield [mailto:[EMAIL PROTECTED] Sent: Sunday, August 03, 2003 1:54 AM To: CF-Talk Subject: Re: CFC Addressing On Saturday, Aug 2, 2003, at 05:59 US/Pacific, Jason Blum wrote: Does anyone happen to know whether one's calling template and one's CFCs can reside in separate security sandboxes? For instance, could an ISP put all client sites in one default security sandbox with few permissions/tags/etc, but then allow them to tie into CFCs in another sandbox that does have all permissions. This would make security, availability and code reuse realitic goals! The security system is per instance, i.e., each CFMX instance has its own sandbox security. If you had multiple CFMX (for J2EE) instances on a server, you could define the same shared CFC directory as a custom tag path in each instance and therefore reuse CFCs across multiple instances. However, the security applied would be that for each individual CFMX instance, therefore the same CFCs would be subject to potentially different security rules in each CFMX instance. Sean A Corfield -- http://www.corfield.org/blog/ If you're not annoying somebody, you're not really alive. -- Margaret Atwood ~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribeforumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. http://www.cfhosting.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Re: CFC Addressing
You can access CFCs just like you would access custom tags. They can be put in the customtags directory of the ColdFusion installation. Or they can be in a directory that you can access via a ColdFusion mapping. Or they can be in the same directory as the page that invokes it. ( Or a relative directory to the page that invokes it ) At 10:52 AM 11/25/2002 -0600, you wrote: I have just finished Hal Helm's CFC book for the second time and this stuff is looking pretty nice. (of course I started programming in OO, so I knew it would be useful). My question is with regards to addressing a CFC. All of Hal's examples were directly under the MX wwwroot directory. How do you address a CFC if it is not under the wwwroot? For example, on my laptop, I have a virtual directory setup in IIS to point to d:\sandbox for my testing/play area. How would I invoke a cfc here? Would this also not be a problem for shared/virtual hosting where you might or might not know where the wwwroot folder is? This does not sound real portable if you have to have a 'physical' path to the wwwroot? Thanks -- Jeff ~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribeforumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm
Re: Re: CFC Addressing
That's not totally true. You can only sort of address CFCs relatively. You can't for example go up a directory, i.e. ../CFCs/ Which frankly, is rather annoying. ** You can access CFCs just like you would access custom tags. They can be put in the customtags directory of the ColdFusion installation. Or they can be in a directory that you can access via a ColdFusion mapping. Or they can be in the same directory as the page that invokes it. ( Or a relative directory to the page that invokes it ) At 10:52 AM 11/25/2002 -0600, you wrote: I have just finished Hal Helm's CFC book for the second time and this stuff is looking pretty nice. (of course I started programming in OO, so I knew it would be useful). My question is with regards to addressing a CFC. All of Hal's examples were directly under the MX wwwroot directory. How do you address a CFC if it is not under the wwwroot? For example, on my laptop, I have a virtual directory setup in IIS to point to d:\sandbox for my testing/play area. How would I invoke a cfc here? Would this also not be a problem for shared/virtual hosting where you might or might not know where the wwwroot folder is? This does not sound real portable if you have to have a 'physical' path to the wwwroot? Thanks -- Jeff ~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribeforumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm
