Andrea Magni

This feature (retrieving response content provided by the server even when an http error occurs) is now implemented in MARS client library. Check this demo: https://github.com/andrea-magni/MARS/tree/master/Demos/ErrorObjects BTW: I've also added a mechanism to implement this behavior on the server side. Sincerely, Andrea

Hi Stuart, have you generated your application using MARSCmd and selecting the MARSTemplate folder? I don't recognize that datamodule... BTW: MARS creates an instance of the resource per request. So if you have a TDatamodule descendant decorated with MARS attributes and registered as a REST resource, a new instance will be create per each incoming request. The TFDConnection, consequently, will be created too. The key point for using (FireDAC) connection pooling is pass through connection definition names (with Pooled parameter set to True) and not configuring the connection as one would do in a standalone application. Sincerely, Andrea

You can drive the serialization through the serialization options. Sincerely, Andrea

Hi, what do you mean with "created the sample code"? I just pulled the most recent version from the repo, run MARSCmd_VCL and created a new project from the template. Everything compiles just fine Win32 and Win64 with my Delphi 12.1... Let me know how to reproduce the error. Sincerely, Andrea

Hi, now I get what you meant, sorry. To design your API in OpenAPI 3 format (for example) and to have the corresponding API implemented in MARS. This is something I'd like to add as a feature but I would say not in the immediate future. I've added (in the past) OpenAPI3 support to MARS, meaning the library will emit an OpenAPI3 description of your API (the other way around with respect to what you are asking). It would be a nice addition to cover your use case. I'll let you know if I'll find time to implement it (of course I would appreciate contribution as MARS is an OS project so if you feel to contribute, you are welcome!). Sincerely, Andrea

Hi, you can start following instructions to install the library, if you haven't already. Check this link: https://github.com/andrea-magni/MARS/blob/master/docs/Installation.md After that, find, compile and run the MARSCmd utility ( Utils/Source/MARScmd folder in your repository clone). It will guide you through a simple wizard to startup your first MARS application, cloning the Demos/MARSTemplate project group. You should have your first MARS REST server application up and running in 1 minute. Sincerely, Andrea

Hi, I never faced this specific issue. I know for sure many people are successfully using MARS in different scenarios. Maybe this is a false positive (it happened more than once to see false positive with Delphi built software, even simple VCL applications). You may want to check the executable agains an online antivirus like virustotal or the like... Sincerely, Andrea

Hi, yes you can easily read request's header: 1) using the HeaderParam attribute to decorate a field of your resource (or an argument of your method) to retrieve the value 2) accessing the IMARSActivation and the Request field to have a more direct access to the underlying request object Other thing is to use that header to provide authentication/authorization through MARS built-in facilities. We can explore that too, just let me know what you need and some examples of requests. Sincerely, Andrea

Hello Ertan, you may want to check the AfterInvoke capabilities: - you can define a local method in your resource class that will be called after the request has been executed, yet before connection is closed; that seems a good place to cleanup temporary files - there is also a global mechanism ( look for TMARSActivation.RegisterAfterInvoke in Server.Ignition.pas in the MARSTemplate Demos folder). Hope this helps, let me know if you need something more. Sincerely, Andrea

Dear Kostas, firstly I want to apologize not being much available these months. I've been very busy and many things fell behind. The easiest way to log errors in MARS is to provide an InvokeError handler: TMARSActivation.RegisterInvokeError( procedure (const AActivation: IMARSActivation; const AException: Exception; var AHandled: Boolean) begin CodeSite.SendError('Error: ' + AException.Message + ' Path: ' + AActivation.URL.Path); end ); There is an (empty) example of this in Server.Ignition.pas unit of the MARSTemplate (Demos folder). Hope this helps! Sincerely, Andrea

Hi @ertank, I managed to reply to your issue on GitHub: https://github.com/andrea-magni/MARS/issues/115 Sorry everybody for the late, I'll try to keep up with all questions ASAP. Sincerely, Andrea

I saw that too. I meant in the code above a genDictEnum.Free is missing somewhere before mc.Free call. Thanks

Hi @John Kouraklis and @Remy Lebeau, thanks for this topic that helped me too. Just wanted to add I think we should free the enumerator object (returned by TDictionary<>.GetEnumerator). I've used this approach in MARS REST library, as you can see here: https://github.com/andrea-magni/MARS/blob/41fd78e5416e38fad0f6a0451402a10824aa62c4/Source/MARS.YAML.ReadersAndWriters.pas#L222 Thanks again you both. Andrea

Hi @Galina, sorry for the late reply. MARS is pretty compatible with older Delphi version up to XE... This is true especially for the server side. The client side has some features relying on the Parallel Programming Library (thus XE7+) but should compile with older version too. Let me know if you encounter issue compiling with older Delphi versions, I will try to help. Sincerely, Andrea

As you can see here: https://github.com/andrea-magni/MARS/blob/f3c2396eeac4df9b1f9a4d4ef640d95bb6dd569d/Source/MARS.Core.MessageBodyWriters.pas#L217 It is a really straightforward implementation and I guess yours is not much different. The StreamToBase64 and StringToStream functions are also available just in case you need them. Let me know if there's anything I can help with! Thanks, Andrea