[erlang-questions] Erlang and the TDS protocol

[CGS]

Hi Marcel,

I suppose the reason for using C wrappers is coming from the compatibility
with the native language in which that particular SQL application is
developed.

I do agree that a solution based on TCP server would be at least more
readable and maybe more suitable for clustering SQL servers. Nevertheless,
that's the choice of developers. Speaking for myself only, I would go with
your option because I see no downfall to that and it would provide a less
dependable interface.

This is my 2c opinion. If someone has a better explanation/suggestion,
please, by all means, correct me.

CGS




On Wed, Jun 6, 2012 at 8:22 PM, Marcel Meyer <marcel.meyer@REDACTED> wrote:

> Hi David,
> No replies yet. I was wanted to see how other db wire protocols were
> implemented, and saw that 'dizzyd' did the mysql driver natively. I spoke
> to a colleague of mine and we wondered if there might be performance issues
> with bit syntax and that the ODBC app wanted to go straight to the metal.
> The reason I was asking this is that we're talking about how you would
> build a proxy to a cluster of Sql Servers (not a Sql Server Cluster).
> Jan Kneschke of lighttpd fame is working on a MySql proxy, with
> failover/load balancing properties. Could be interesting for Sql Server...
>
> Regards,
> M
>
> On Wed, Jun 6, 2012 at 1:07 PM, David Mercer <dmercer@REDACTED> wrote:
>
>> Just checking to see if anyone replied to you on this and did not
>> reply-all the list.  I would be interested in hearing the answer, too, if
>> one is available.****
>>
>> ** **
>>
>> Cheers,****
>>
>> ** **
>>
>> DBM****
>>
>> ** **
>>
>> *From:* erlang-questions-bounces@REDACTED [mailto:
>> erlang-questions-bounces@REDACTED] *On Behalf Of *Marcel Meyer
>> *Sent:* Sunday, June 03, 2012 4:39 PM
>> *To:* erlang-questions
>> *Subject:* [erlang-questions] Erlang and the TDS protocol****
>>
>> ** **
>>
>> Dear list,****
>>
>> ** **
>>
>> I am curious why there isn't a native Erlang TDS protocol implementation.
>> Even /otp/lib wraps a C ODBC implementation using a port.****
>>
>> Would this not be simpler and more concise using bit syntax, since the
>> TCP datagram unpacks in 1 line of code (more for readability, of course)?
>> ****
>>
>> It just seems like extra work: C wraps the msg, port wraps C, ODBC app
>> wraps port etc. There is a lot of 'wrapping' going on.****
>>
>> ** **
>>
>> Any input would be much appreciated.****
>>
>> ** **
>>
>> Kind regards,****
>>
>> Marcel****
>>
>> ** **
>>
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20120607/29040e8a/attachment.htm>