[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: Klaus Malorny <Klaus.Malorny@knipp.de>, Eugenio Pinto <eugenio.pinto@fccn.pt>
CC: <ietf-provreg@cafax.se>
From: James Gould <jgould@verisign.com>
Date: Wed, 31 Oct 2007 13:31:25 -0400
In-Reply-To: <4728B17F.3050808@knipp.de>
Sender: owner-ietf-provreg@cafax.se
Thread-Index: Acgb49xxGzhI6YfXEdyH7gAX8s02Pg==
Thread-Topic: [ietf-provreg] Re: EPP over HTTP or simple TCP?
User-Agent: Microsoft-Entourage/11.3.3.061214
Subject: Re: [ietf-provreg] Re: EPP over HTTP or simple TCP?

I agree that the processing time for the validation is a slight impact
depending on the parser being used and whether you're utilizing schema
caching.  We do schema validation with all of our servers.

-- 


JG 

-------------------------------------------------------
James F. Gould
Principal Software Engineer
VeriSign Naming Services
jgould@verisign.com
Direct: 703.948.3271
Mobile: 703.628.7063

 
21345 Ridgetop Circle
LS2-2-1
Dulles, VA 20166

Notice to Recipient:  This e-mail contains confidential, proprietary and/or
Registry  Sensitive information intended solely for the recipient and, thus
may not be  retransmitted, reproduced or disclosed without the prior written
consent of  VeriSign Naming and Directory Services.  If you have received
this e-mail message in error, please notify the sender immediately by
telephone or reply e-mail and destroy the original message without making a
copy.  Thank you.


> From: Klaus Malorny <Klaus.Malorny@knipp.de>
> Date: Wed, 31 Oct 2007 17:46:55 +0100
> To: Eugenio Pinto <eugenio.pinto@fccn.pt>
> Cc: <ietf-provreg@cafax.se>
> Subject: Re: [ietf-provreg] Re: EPP over HTTP or simple TCP?
> 
> Eugenio Pinto wrote:
>> Stephane and Klaus,
>> 
>> Thanks for your quick feed-back.
>> 
>> Regarding the TCP transport protocol on RFC 4934 you are right, it was
>> my mistake to talk about the "end-code" if we have the leading length
>> field.
>> 
>> However the main reason for my email was the implementation part:
>> 
>> Have you implemented the TCP approach? If so, did you implement a TCP
>> server from scratch or you used the source code from a server like Tomcat?
>> 
>> 
> 
> We (CORE) use our own Java implementation of EPP. As a part of it, we
> developed 
> an EPP toolkit that can be used both on client and server side and that does
> validation. Without having actually measured it, I don't think that the
> validation has a big impact on the overall processing times, compared to the
> time required to perform the database transaction(s). From a programming
> perspective, it is a clear advantage, as it simplifies the dissection of the
> EPP 
> request. You don't need to check the existence of every element and attribute,
> as you *know* that they exist due to the preceding validation. On the other
> hand, it is important to point out that a successful validation is only a
> necessary condition, but not a sufficient condition that the incoming EPP
> request is valid. There are still a lot of cases that need to be tested.
> 
> For the actual I/O, we do not rely on a third party product like Tomcat.
> 
>> [...]
>> 
>> Regards,
>> Eugenio
> 
> Regards,
> 
> Klaus
> 
> -- 
> ____________________________________________________________________
>       |       |
>       | knipp |               Knipp  Medien und Kommunikation GmbH
>        -------                       Technologiepark
>                                      Martin-Schmeißer-Weg 9
>                                      44227 Dortmund
> 
>       Geschäftsführer:               Registereintrag:
>       Dietmar Knipp, Elmar Knipp     Amtsgericht Dortmund, HRB 13728
> 
> 
> 



Home | Date list | Subject list