Re: 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