While I understand the point about web server mappings, that does not make
them a fault -- I prefer nuance :) -- and we have not met any hosts that
have an issue with it (yet -- I guess).  Anyhow, we are always looking for
new ideas to improve upon the code, so please feel free to share your ideas
for, perhaps, removing this part of the setup.

BTW: I love the MX Coding Standards Doc!!!!!

HAPPY HOLIDAYS

-- 
Regards,
Michael J. Sammut
____________________________________________________________________
F O U R  E Y E S  P R O D U C T I O N S

think | plan | create :: web site design & development  :: NYC

E. [EMAIL PROTECTED]  |  T: 718.254.9557 ext. 101  |  F: 718.254.0399

W. http://www.foureyes.com




"Sean A Corfield" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> On Dec 21, 2003, at 11:52 PM, Gary Menzel wrote:
> > So - when you are calling the Admin site you are using
> > http://127.0.01/farcry ?
>
> Yes, like I say, that's correctly producing the login screen. And I can
> get the basic FarCry app up as well. The problem is that when I login -
> with the correct username/password - it doesn't seem to set the session
> variables correctly after <cflocation> so it never thinks I'm logged
> in.
>
> I guess my primary objection to the setup is that FarCry seems to
> *require* web server level virtual mappings which I think is very
> intrusive and it also does not respect the context root in an
> application (assuming the context root is /) - these both make FarCry a
> 'no-no' for use here at Macromedia so I hope those faults can be
> rectified.
>
> (And don't get me started on the Hungarian prefix naming convention
> used in the code! LOL!)
>
> Sean A Corfield -- http://www.corfield.org/blog/
>
> "If you're not annoying somebody, you're not really alive."
> -- Margaret Atwood
>
>
>



---
You are currently subscribed to farcry-dev as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]

MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004

Reply via email to