Actually, my workaround is just about exactly the same thing you are
doing. Unfortunately this uses the system datetime from CF, and not
the DB. With a cluster of 3 CF machines and one DB machine this could
result in 3 different times (if all the system times aren't
synchronized properly).
I
Hmm, well, this may be a crazy idea, but here's what I'd do if I
needed to accomplish what you are suggesting, which is to always
return the same, synchronized datetime value regardless of which CF
server the code was running on:
I'd create a DateHelper object with a getNow() method that would
Yeah, that would be another way to solve the problem. In my case I
suspect it would be easier just to spend a little time and get the
time on all the servers in sync.
This is one of those problems where I started by trying to wedge
something into Transfer that it doesn't really do in a very
