Greetings,
Depending on the number of developers and how often they change, virtual hosts are good.
Set up a sub-domain for each developer, ie jim.my-company.co.nz.
Then they can configure there local setup to there hearts content, seperate CVS/document tree, also get separate logs.
instance for the developer to crash 50 times a day
It is the ultimate object oriented programmer methodology...
Stuart Frew wrote:
Greetings,
Depending on the number of developers and how often
This is an even more pronounced problem with sessions IDs in
URLs, though. With cookie based session tracking, the second
browser window will send the same cookie that the first browser
window received.
And there lies the rub.
The user is using the system to process client A. The cookie
Opps forgot to CC the list
--
Cheers Stuart
---
New Zealand Revolution
[EMAIL PROTECTED]
+64 9 918 7663
On 24 May 2001 14:57:09 -0700, ___cliff rayman___ wrote:
Stuart Frew wrote:
On 24 May 2001 14:21:32 -0700, ___cliff
Greetings,
One problem with using cookies for session management is that the user
can have two browsers open doing the same process.
Which means the first cookie Session ID will be over writen by the
second one. Which can lead to horrid results if the user continues the
first process but has
From my experiance with using the Enterprise solutions is that you pay a
yearly maintenace to be told to upgrade to a the next version.
Also you can create unmaintainable spagettie not matter the tool.
As to intergration support, I have found that when you really need that
intergration feature
