You can share something with me?, tks.
I would like to develop a backend with Indy to hear and reply information using a ISO and a front end in IW to see this information formatted.
@JNPSoftware ok, so what's stopping you? What are you stuck on exactly?
I've read that I could use "TClientSocket" for this, but I find it weak
@rlebeau It's a good idea develop a server to receive and a client to response this messages or do all in one place?
but you said you wanted an IW frontend, but IW is web-based so its also a backend, too. Unless you mean you want IW communicating with yet another backend, then it would make sense to use Indy for communications between IW and that other backend, in which case you would likely have IW act as a server for the web browser and a client for the other backend
@rlebeau, i'm sorry, i'm confusing things. I would like to develop separated parts. IW is accessing a database with information of cards numbers, value, transactions list, etc.
Indy server receive/write ISO messages and use a same database of IW. But they are totally separated.
Indy server receive/write ISO messages and use a same database of IW. But they are totally separated.
I'm will act like a bank for authorizing a card transaction. I will receive ISO messages from another systems. this is my problem, how can i create a server to receive these messages, and response then in a ISO format.
Since EMBT forums are funky/down again.. .we have put some Delphi as well as Indy forums up to test.. join in!
@JNPSoftware well, the ISO 8583 protocol is fairly straight forward (see https://www.codeproject.com/Articles/100084/Introduction-to-ISO), so what is not clear about it to you exactly? Do you even know how to use Indy in general? Let's start with that.
implementing http clients and servers is easy with indy..
@mterwoord @lbehm It is a little more involved than that. CalDAV is an extension to WebDAV. It is basically iCalendar wrapped in XML and transmitted with WebDAV over HTTPS. Indy does has a (very) minimal WebDAV client ,
TIdWebDAV, but no WebDAV server. I'm sure a CalDAV client/server could be made with TIdHTTP/TIdHTTPServer, with some manual work
@lbehm There are plenty available (https://devguide.calconnect.org/CalDAV/libraries/, http://libcaldav.sourceforge.net, etc), but none using Indy that I am aware of.
There are Indy forums over here too on the linked web forums.
https://www.atozed.com/2018/04/embt-squirrel-on-vacation-again/
^^ Embarcadero Squirrel on Vacation Again
The squirrel on a wheel which powers the Embarcadero Forums has gone on vacation – again. The Embarcadero forums are thus down and....
The squirrel on a wheel which powers the Embarcadero Forums has gone on vacation – again. The Embarcadero forums are thus down and....
More important: how would you import a TGraphic into a TIdAttachmentMemory?
@lbehm See http://www.indyproject.org/Sockets/Blogs/RLebeau/2005_08_17_A.aspx and http://www.indyproject.org/Sockets/Blogs/RLebeau/20080116.aspx for how to produce HTML emails with embedded images. As for using TGraphic, you can save it to a TStream first, such as TMemoryStream, and then construct the TIdAttachmentMemory from that TStream. Or, you can save the TGraphic to a temp file and use TIdAttachmentFile with its FileIsTempFile property set to True so the file will be deleted when the attachment is freed. Or, you could write your own TIdAttachment class that overrides OpenLoadStream() and CloseLoadStream() to return/free a temp TStream that the TGraphic has been saved to and which Indy will read from to get the data to send.
@rlebeau I ended up creating multiple message parts:
text/html, text/plain, multipart/alternative, multipart/related... And figured out that TIdMessageClient.SendBody() goes into an endless loop if the message parts aren't created in the correct order. I create every part with new TIdText(pMessage->MessageParts, NULL) and set the correct ParentPartid. Is there a way to reorder them based on the ParentPart id?
@lbehm yes, order matters (the parts are sent in the order they are listed, and MIME is very sensitive to the order - something I plan to address in the future: IndySockets/Indy#139), however I have never seen
SendBody() get stuck in an infinite loop before. Can you provide an example that causes this?
@rlebeau I think I ended up here: https://github.com/IndySockets/Indy/blob/master/Lib/Protocols/IdMessageClient.pas#L1373
Something like this should break it:
TIdText *t = new TIdText(pMessage->MessageParts, NULL);
t->ContentType = "text/plain";
t->Body->Text = "Test";
TIdText *h = new TIdText(pMessage->MessageParts, NULL);
h->ContentType = "text/html";
h->Body->Text = "Test";
TIdText *a = new TIdText(pMessage->MessageParts, NULL);
a->ContentType = "multipart/alternative";
a->ParentPart = -1;
t->ParentPart = a->Index;
h->ParentPart = a->Index;
I intended to build up the message parts as they are needed. If someone just sets the
text/plain content no message part is needed. If HTML is added, the text/plain is converted and both parts are appended to the alternative part. Same with related if a graphic is added earlier or later.