Comments on: DataSnap 2010 – sending and receiving objects

By: Andreano Lanusse

Andreano Lanusse — Wed, 21 Aug 2013 04:05:43 +0000

In reply to Paulo Alexanre. @Paulo, quando o retorno for null testa algo assim if not Assigned(Objeto) then ....

By: Paulo Alexanre

Paulo Alexanre — Wed, 14 Aug 2013 18:44:16 +0000

Quando eu não quero retornar objeto nenhum e retorno nil no servidor, as classes proxy geram uma exceção de que não pôde converter TJSONNull em TJSONObject.. isso é normal? o que eu posso fazer para retornar null ou tjsonnulll ?

por exemplo uma consulta de um cliente que nao existe.
Obrigado!

By: Andreano Lanusse

Andreano Lanusse — Tue, 05 Oct 2010 05:35:17 +0000

In reply to Alin. Yes, TStream is part of the data types supported by DataSnap

By: Alin

Alin — Sun, 03 Oct 2010 15:14:32 +0000

if my object has a TStream property will the above code work ?

By: Failover Server in DataSnap and Delphi 2010 | Delphi básico: Lo más básico de Delphi

Sun, 11 Apr 2010 17:19:29 +0000

[…] DataSnap 2010 – sending and receiving objects […]

By: Luigi D. Sandon

Luigi D. Sandon — Sat, 03 Apr 2010 12:33:22 +0000

I wonder if one of the design goals of Datasnap 2010 was to use as many fashionable buzzwords as possible.
Why Datasnap 2010 lacks an efficient binary transfer protocol? JSON was designed for a language that can’t handle binary data easily. Delphi can. JSON should be just one ot the transports when compatibiity with other technologies is important. But applications that need to move large amount of data among Delphi applications whu should go through inefficient string encodings? Otherwise it is easier to send a socket port, open the socket and perform a binary transfer. Even WCF understood it and offers a “binary XML” format where compatibility is not needed but performance are.
I guess I am not going to migrate our DCOM Datasnap applications to this technology until it starts to offer everything DCOM offers. Or I will migrate to another RPC technology that would allow us to buy Delphi Professional instead of the Enterprise. It would be a huge saving – given the higher SKU is now offering only low-end solutions.

By: Leonardo M. Ramé

Leonardo M. Ramé — Fri, 02 Apr 2010 22:52:01 +0000

Thanks Andreano for this post.

I didn’t test this code, but by reading it I can’t figure out where the call to GetJSONCustomer is executed, from the client side.

I think the call should be in line 8 of the last code snippet:

myJSONCustomer := JSONToCustomer(proxy.GetJSONCustomer);

Leonardo.