On Wed, 7 Mar 2001, Charles Daminato wrote:
> Also, it may not take more than a day - we just can't spare a programmer to
> do that yet. There are other implications - prevent hammering? Do we give
get real. The whole point is to alleviate the current hammering, and
either you already have that logic and can reuse it, or you don't and it's
a bogus argument. (Sounds like the access control argument that was
presented _many_ moons ago...)
> customized formats? (i.e. selectable fields to report)
No. At least not yet. If you provide a format that's simple enough to
import into a spreadsheet, then clients can pull out the columns they
want.
And you can add more fields/columns down the road if you want. Take
something that's easy enough to do... and build on it later.
> What information do we provide? Simple contact information, or
> transaction audit? (audit being
... well, this would be good stuff to have... but do you really think it
will ever get implemented if we wait for the complete system? There are
new TLDs coming down the road quickly, and if the .ca fiasco was anything
to measure by, those are going to be significant consumers of staffing
resources. My vote would be for a quick dump of the information that is
already available...
transaction details would be Fantastic, but a straight list of what's
shown in the view_domains pages should be a trivial start.
> more expensive to the system than just plain info) - many questions. We
> have to design it, code it, test it, train internally, then release it - and
> fix bugs along the way, hopefully not tooooooo many by the time it gets to
> you folk. This'll take more than a day :)
I'd suggest taking a lesson from the original netscape team. Implement
something now, improve and enhance it later.
>
> Charles Daminato
> Product Manager (ccTLDs)
> Tucows Inc. - [EMAIL PROTECTED]
-Tom
