Integration with Mason

Has anybody had any experience with TeamSite/Mason/Apache Integration?

I going to try to use the mod_iw_ts_rewrite.so module which is used for SSI's.

Its a long shot. Can TeamSite Integration with Mason/Apache??...

John Cuiuli
Consultant
Sydney, Australia

Find more posts tagged with

Comments

laj1

Teamsite should be able to integrate with masonic Apache.

A bunch of us have integrated it with cold fusion, or ASP. There's little difference.

You'll need an apache with mason (obviously), configured to use the teamsite file store as its document tree.
Then you'll need to make teamsite redirect preview requests to your masonic Apache.

In my case, I have cold fusion running on my teamsite server, it is front ended by the IIS which is also installed on my teamsite server (win2k). I probably could have put CF on a different machine, and used either distributed mode, or IIS redirect.

I'm sorry that this reply is light on do's and don'ts, but not knowing how you're set up, I can't offer more than general advice.

In the end, you need some way for the preview URLs to eventually get mason to render a page. hardware/software architecture will have a lot to do in determining how.

Len.

Len Jaffe
My Heart Is A Flower
Update your DevNet profile - let us know who you are!

Johnny

Thanks for your post.

Trying it out is probably the only way to find out.

I haven't got much info, because I don't know too much about Mason.
Just trying to see if anyone else has tried this.

From what I understand Mason isn't a separate server, rather an add-on to Apache, much like SSI's.

So to me, this means I cant use the IW proxy to catch Mason requests as they are processed internally by Apache which is great.

The only mystery I have so far, is how will Mason resolve page includes.

There is a redirector module that is installed for SSI/TeamSite integration, so I'm guessing something similar will be needed.

Ill let you know how I go.

John Cuiuli
Consultant
Sydney, Australia

laj1

From what I understand Mason isn't a separate server, rather an add-on to Apache, much like SSI's. 

Mason is a set of Perl modules (Mason.pm). It floats in the foam on top of mod_perl, and is invoked as a mod_perl
handler. See your mod_perl documentation, or O'Reilly book for details.

So to me, this means I cant use the IW proxy to catch Mason requests as they are processed internally by Apache which is great. 

Teamsite has to be configured to pass the mason request to the mod_perl/mason-equipped Apache server. That server has to have the Teamsite document store "mounted" as some part of its document tree, and has to be configured to run mod_perl/mason.

The only mystery I have so far, is how will Mason resolve page includes.
Again, the Teamsite file store must be available to your Apache/Mason server. relative paths inside your Mason code will go a long wa toward making htis easier.

Len.

Len Jaffe
My Heart Is A Flower
Update your DevNet profile - let us know who you are!

Johnny

Maybe we are just misunderstanding each other,

but you pretty much just repeated what I said.

Thanks for the help though!

John Cuiuli
Consultant
Sydney, Australia