[cfaussie] Re: Inter-Application Comms

2007-10-30 Thread Brett Payne-Rhodes

Thanks everyone,

I already use a http post based system but am thinking that a cfc might be more 
appropriate, and more secure, these days - though http is still the simplest to 
use.

Thanks for all the suggestions!

Brett
B)


Brett Payne-Rhodes wrote:
 I have a CMS that runs as a separate sub-domain to the actual site being 
 administered. On occasion (and seemingly more and more) there is a need for 
 the CMS to tell the website that some update has been made and that it should 
 reload application and/or session variables. And a recent requirement is for 
 the notification to come from an entirely different application.
 
 Before I launch into a complete rewrite of the current system, which predates 
 webservices, I was wondering what methods others on this list might be using 
 that they would recommend. The two key features being simplicity and 
 security, which I agree are probably conflicting, but hey...
 
 Cheers,
 
 Brett
 B)
 
 
  
 
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
cfaussie group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cfaussie?hl=en
-~--~~~~--~~--~--~---



[cfaussie] Re: Inter-Application Comms

2007-10-30 Thread Simon Haddon
You have to remind yourself that calling a webservice cfc is just making a
http request anyway.  Sure it builds the SOAP structure for you but the
security has to be taken care of just the same.

Cheers,
Simon

On 31/10/2007, Brett Payne-Rhodes [EMAIL PROTECTED] wrote:


 Thanks everyone,

 I already use a http post based system but am thinking that a cfc might be
 more appropriate, and more secure, these days - though http is still the
 simplest to use.

 Thanks for all the suggestions!

 Brett
 B)


 Brett Payne-Rhodes wrote:
  I have a CMS that runs as a separate sub-domain to the actual site being
 administered. On occasion (and seemingly more and more) there is a need for
 the CMS to tell the website that some update has been made and that it
 should reload application and/or session variables. And a recent requirement
 is for the notification to come from an entirely different application.
 
  Before I launch into a complete rewrite of the current system, which
 predates webservices, I was wondering what methods others on this list might
 be using that they would recommend. The two key features being simplicity
 and security, which I agree are probably conflicting, but hey...
 
  Cheers,
 
  Brett
  B)
 
 
  
 
 


 



-- 
Cheers
Simon Haddon

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
cfaussie group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cfaussie?hl=en
-~--~~~~--~~--~--~---



[cfaussie] Re: Inter-Application Comms

2007-10-29 Thread Steve Onnis

You could use CFHTTP to hit a page on the website to reload the app?  If
there is a config file or db that holds users you could authenticate against
that to handle the security side of things.

Another way is to in your app use the cfapplication tag and make the app
name the name of the app you want to reload and perform the tasks you need
after calling the cfapplication tag and then switch it back:-

cfif needsToReload

cfapplication name=fontendWebsite /
!--- Do the stuff to reload the application ---

cfapplication name=theActualApplication /
!--- Continue happily ---

/cfif 

-Original Message-
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of Brett Payne-Rhodes
Sent: Tuesday, 30 October 2007 2:22 PM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Inter-Application Comms


I have a CMS that runs as a separate sub-domain to the actual site being
administered. On occasion (and seemingly more and more) there is a need for
the CMS to tell the website that some update has been made and that it
should reload application and/or session variables. And a recent requirement
is for the notification to come from an entirely different application.

Before I launch into a complete rewrite of the current system, which
predates webservices, I was wondering what methods others on this list might
be using that they would recommend. The two key features being simplicity
and security, which I agree are probably conflicting, but hey...

Cheers,

Brett
B)





--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
cfaussie group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cfaussie?hl=en
-~--~~~~--~~--~--~---



[cfaussie] Re: Inter-Application Comms

2007-10-29 Thread Andrew Scott

I would recommend REST.

It uses XML-RPC, and integrates security in each request to be
authenticated.



Andrew Scott
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613  8676 4223
Mobile: 0404 998 273


-Original Message-
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of Brett Payne-Rhodes
Sent: Tuesday, 30 October 2007 2:22 PM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Inter-Application Comms


I have a CMS that runs as a separate sub-domain to the actual site being
administered. On occasion (and seemingly more and more) there is a need for
the CMS to tell the website that some update has been made and that it
should reload application and/or session variables. And a recent requirement
is for the notification to come from an entirely different application.

Before I launch into a complete rewrite of the current system, which
predates webservices, I was wondering what methods others on this list might
be using that they would recommend. The two key features being simplicity
and security, which I agree are probably conflicting, but hey...

Cheers,

Brett
B)




--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
cfaussie group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cfaussie?hl=en
-~--~~~~--~~--~--~---