Re: Inclusion of Legacy Code

[Tom King]

That's a smidge vague...

You could a) chuck cfc's into the misc folder, b) add folders then put them in the URL rewrite exclusion list, c) cut and paste code into respective view functions etc..

Without knowing what you're referring to, it's hard to be of more help.

On Wednesday, 22 May 2013 19:45:04 UTC+1, The Broox wrote:

I was wondering if there is a way to integrate legacy code into the Wheels framework without altering all the links in said existing code? 

[The Broox]

I have been tasked with revamping my company's intranet site. Right now all the in-house development tools are open to anyone who can access the intranet. Meaning people from Marketing/Sales can access the tools that affect our website (our product). We are small but growing so this wasn't as big a problem a year ago as it is today. I need to secure some of the tools behind a single authentification. I have played with wheels and know how easy it is to throw together registration and login with it. Therefore I was hoping to include the legacy tools into wheels in a "black box" fashion and add an "authentification layer" via new wheels MVCs.

[Tom King]

So in that example, you could hypothetically run wheels alongside the legacy app, but make sure they have the same application names.

They'd then share app/session scopes, which means you could use wheels for authentication and permissions delegation, and then test for the presence of those variables in the other legacy code.

It's not exactly an ideal scenario, but could work.

T