Tell you what, I'll stop complaining about the lack of a standard
interface if OpenSRS's programmers can do the following:
Create two HelloWorld applications that authenticate with
OpenSRS and peform one simple message exchange (e.g. Hello
World).
One written in Java, one written in C#, using only standard libraries.
If they cannot do that in about 10-20 lines of code, then there is
a problem.
I'd gladly write a C# implementation using TCP sockets to share
with everyone, except that I *know* I will run into a problem with
the encryption that will cost me time I am unwilling to spend.
Adam
Colin Viebrock wrote:
> Notwithstanding the above, the encryption portion of the OpenSRS
> protocol was a major pain in the ass. It may use standard encryption
> protocols (DES, Blowfish, CBC, etc.), but it the implementation
> (Crypt::CBC) is *not* standard in anyway. This caused much gnashing
> of teeth and tearing of hair, and eventually I had to "translate"
> Crypt::CBC into PHP before I could even look at the OpenSRS code.
> This wasn't easy, and I would happily agree that it makes porting the
> OpenSRS client to other languages/platforms non-trival.
