[Autoaccept-sink-devel] AutoAccept Sink

[Thomas, C. <ct...@ra...>]

Members of this fairly small community - i have a few questions:
 =

1 - i have setup and made a few tweaks to the existing code which is, as
Daniel Lundeen points out, far superior to what is available from
Microsoft's template.  Has anyone done any comparison or investigation
into how much slower (which it is likely nominally as it has more flow
and debug logic built in than one might need) over a striped down
version you might build using Microsoft's template.  Daniel - you have
an environment that is approximately an order of magnitude greater than
ours - might i ask how many mailservers the 800 mailboxes are
distributed accross?  We'll initially be running the sink on a single
server hosting ~90 mailboxes dedicated to our conference rooms.
 =

2 - after i went through this learning process, i decided that, given
our core information architecture, it would be best served in C#.  Thus,
i have embarked on an effort to translate this code, in its entirety, to
C# using .Net 2.0 - has anyone else done this?  So far, i have
translated most of the code, with the exception of the code in
modADAccess used to find the global catalog which in turn is only used
to determine the mail address for including the organizer's email
address - which i have for now, decided not to support.  I am stepping
through the compile and build process, cleaning up my ~200 errors in
translation.  Has anyone gone through this excercise?  Explored it?
Laughed it off as an absurd idea?
 =

3 - What improvements have people made - Daniel - you mentioned you made
a few changes - might you share a patch or point out the specific areas
you touched and improved?  =

 =

Thank you in advance.
 =

Cord
............................................................
Cord Thomas
Information Services and Technology (IST)
RAND
1776 Main Street
Santa Monica CA 90407
Phone: 310.393.0411 x6672
e-mail: ct...@ra...
 =



--------------------

This email message is for the sole use of the intended recipient(s) and
may contain privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and destroy all copies
of the original message.