Adam, I would like to come to Paul's defense on this one.
The Portal Connector approach -- provided your client has the license -- comes in handy in a few scenarios: 1)You have a "modular" application running outside LiveServer but LiveServer is serving as the main server. These modular apps can be a "skinned" forum, blog or anything else that you want it up and running quickly but you only have time to stick it together with the main LiveServer app so the global navigation get the users across different apps and run-time. 2)You are using LiveServer to enforce a SSO. You may have already have the Reeport module tracking users in your LiveServer directory or a connected LDAP directory. Protal connector allows you to have uniform session across different run-time. ==== Your advice against Portal connector though, makes sense when you are desinging a application anew. Just my 2-cent worth. Henry Lu On Mon, Dec 1, 2008 at 1:43 PM, Adam <[EMAIL PROTECTED]> wrote: > > For those of you unfamiliar with external dynamics, imagine taking the > Active Template approach and applying it to LiveServer. > > I strongly recommend against using this feature of LiveServer, if for > no other reason than a philosophical one. It's hard for me to come up > with a realistic scenario where external dynamics are needed. Do you > really need to use 2 different scripting languages on a single page? > If LiveServer doesn't do what you need, and ASP does, why are you > publishing the file into LiveServer in the first place? > > Is it because you want to be able to search the ASP file? Fine, > publish the ASP file into LiveServer but don't have LiveServer deliver > the content. Sometimes people don't consider the possibility that > LiveServer can index a file for search without being responsible with > actually delivering the content. > > Is it because you want to take advantage of constraints or some other > LiveServer functionality? Ok, then what is ASP doing for you? Can > ASP be integrated with the LiveServer code through a web service or a > simple include? > > Or is it because you don't want to migrate the ASP code? If the ASP > code can be changed to LiveServer, that is usually a good option. It > might take a little more time today, but the benefit is that you > reduce the amount of code you need to maintain in the future. > > But just like you need to be careful with Active Templates, you should > exercise the same caution with external dynamics. It is not a > scalable solution. Think about what you're doing: LiveServer is > creating a physical file, putting that file in a directory that is > available to a web server, making a request for the file through the > web server and then returning the results. That's a lot of processing > for something of questionable value. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/RedDot-CMS-Users?hl=en -~----------~----~----~----~------~----~------~--~---
