It's difficult for me to discuss dates, as this feature is small piece of the puzzle that if much larger infrastructure work. Due to that, there is less certainty than I'd like to have.
I understand that you need to make a decision though, so I'll try my best. Current discussion are for this feature to be available on domains in 6 months or so, but I can see it easily being pushed around, so to expect delivery btw. 6-12 months from today sounds about right. Thanks. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Onno > Molenkamp > Sent: Thursday, July 28, 2005 7:18 AM > To: [email protected] > Subject: Re: [domains-dev] processing results of asynchronous actions > > > Zeljko Dimic wrote: > > Good news: We're aware that notifications mechanism could/should be made > > more usable. Right now, we've got project that will introduce > intelligent > > poll mechanism to see updates to asynchronous orders/actions > (UI and API). > > You would be able to acknowledge reviewed updates, so that next > time, you > > get only new ones. > > This sounds great! > > > BTW, we've considered email, but due to unreliability have chosen > > intelligent poll, rather than push technology, so you can > process it when > > you're ready. > > I don't think it's unreliable, and you can also process emails whenever > you want to, but what you propose sounds just as good to me. :) > > > This features is coming really soon, (app. 1 month to Live > date), but first > > release will be applicable to email service only. We will expand on this > > mechanism for all services we offer, including domains, in a staggered > > fashion. > > > > Bad news: It will take us some time to get to domains, due to underlying > > difference in infrastructure. > > Can you say anything about when you expect it will be available? Will it > be 2 months, 6 months, a year? I have to decide whether I'm going to > implement automatic processing of OpenSRS requests first using the > current API, and then switch over this new polling mechanism, or wait a > while longer and then do it the right way from the start. > > Onno Molenkamp > VEVIDA Services BV > _______________________________________________ > domains-dev mailing list > [email protected] > http://discuss.tucows.com/mailman/listinfo/domains-dev > _______________________________________________ domains-dev mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-dev
