datasnap

Considering the following: We have a 32 bit Datasnap server installed on a 64 BIT Windows Server In embarcadero\rad studio\11.00\redist are 2 folders : 32 bit and 64 bit, with in each a midas.dll. Wich file should we put where? In windows\system32 or windows\syswow64 ? Never put anything in the Windows system directories (unless you have a very, very, very good reason to write there). It's a very bad practice (dating back to Windows 3.x times and poor developers skills, because those dirs are always in the search path) just leading to troubles (i.e. if another application chnages your DLL with

I need to send a simple JSON object to a Restful datasnap server (Delphi) from a Delphi client. I am using Delphi XE. Can anybody help me out with the code? I am trying for hours but not getting it.. Please ask if details are not sufficient Edit: Here is server side method declaration: procedure updatemethodnme(str:string):string; and here is client side code: function PostData(request: string): boolean; var param: TStringList; url, Text,str: string; code: Integer; http: TIDHttp; begin Result:= false; http:= TIDHttp.Create(nil); http.HandleRedirects:= true; http.ReadTimeout:= 50000; http

We've created a Datasnap service (with Delphi XE), using Bob Swart's white paper as a guide. It works fine, and we've deployed it to our test server. Now a problem occurs, when we have executed a large number of requests (through JMeter), some sort of memory corruption occurs. Some requests succeed, some fail with an access violation. In the end, it has become so corrupt, that every request to our OWN (not the DSAdmin) methods responds with an access violation. However, I can't get my hands on a stacktrace to get more info, because the exception is already catched in the processing of the

We run a DataSnap Delphi 2009 application on Windows 2003 Server. DataSnap Client and Server are on the same computer, using DCOM over Borland Socketserver. The client runs a background batch job. Sometimes, we discover that the client can not connect to the server application and displays a message dialog on the server desktop indicating for example "Could not connect to server. Network path could not be found." or "Objectexporter not found." Our Delphi client code never uses a message dialog to show errors or exceptions, instead we use try ... except .. finally ... end and logging to handle

We are developing a new, and our first, DataSnap server and client apps. I have added authentication to the server but I cannot dynamically change the login details for the connection from the client. The User and Password in the procedure TServerContainer1.DSAuthenticationManager1UserAuthenticate( Sender: TObject; const Protocol, Context, User, Password: string; var valid: Boolean; UserRoles: TStrings); stays blank. In the client we set the values as such ... DSConnection := TSQLConnection.Create(nil); DSConnection.DriverName := 'DATASNAP'; DSConnection.LoginPrompt := False; DSConnection