E
Errol Sayre
Has anyone else been struck by the rather obvious conclusion that the
Project Center needs to take advantage of Rendezvous?
I've been trying to test why two computers with the same shared projects
sometimes don't update. It seems that some events (I haven't been able to
distinguish why...) just won't share, while others will...
Back to my point. These two computers are sitting next to each other on the
same LAN, (Well, actually one's wired and the other is connected by a
wireless bridge but essentially it's the same LAN) and it takes them
typically three cycles to make the proper synchronizations. I would think
this should be two, but often times the schedules don't seem to match up on
2 cycles so it takes 2 to 3 cycles on each machine (10 to 15 minutes!!!) for
me to be able to test this...
My solution is to give Entourage smarter project synching capabilities:
One, the time interval should be adjustable...
Two, the program should use Rendezvous to to discover other computers on
it's LAN that are sharing a project and let them tell each other "Hey,
you're sharing project X with me, I just made a change and you need to
update, pass it on." Or better yet, "Here's the change I just made to
project X, pass it on."
Anyone else think this a good idea? I do hope Paul and Barry have some clout
with the MS programmers/idea-dudes to be able to submit this idea to them. I
know there are other little "networkgroup" products that use Rendezvous for
similar purposes, but none that do the project management that makes
Entourage such a hot item. I would submit the idea through the feedback
site, but alas, the MS site is so convoluted, I never made it to the right
page...
Anyway, that's a couple of the many cents I have to drop on this mailing
list.
Errol Sayre
Project Center needs to take advantage of Rendezvous?
I've been trying to test why two computers with the same shared projects
sometimes don't update. It seems that some events (I haven't been able to
distinguish why...) just won't share, while others will...
Back to my point. These two computers are sitting next to each other on the
same LAN, (Well, actually one's wired and the other is connected by a
wireless bridge but essentially it's the same LAN) and it takes them
typically three cycles to make the proper synchronizations. I would think
this should be two, but often times the schedules don't seem to match up on
2 cycles so it takes 2 to 3 cycles on each machine (10 to 15 minutes!!!) for
me to be able to test this...
My solution is to give Entourage smarter project synching capabilities:
One, the time interval should be adjustable...
Two, the program should use Rendezvous to to discover other computers on
it's LAN that are sharing a project and let them tell each other "Hey,
you're sharing project X with me, I just made a change and you need to
update, pass it on." Or better yet, "Here's the change I just made to
project X, pass it on."
Anyone else think this a good idea? I do hope Paul and Barry have some clout
with the MS programmers/idea-dudes to be able to submit this idea to them. I
know there are other little "networkgroup" products that use Rendezvous for
similar purposes, but none that do the project management that makes
Entourage such a hot item. I would submit the idea through the feedback
site, but alas, the MS site is so convoluted, I never made it to the right
page...
Anyway, that's a couple of the many cents I have to drop on this mailing
list.
Errol Sayre