Werbung
LEO

Sie scheinen einen AdBlocker zu verwenden.

Wollen Sie LEO unterstützen?

Dann deaktivieren Sie AdBlock für LEO, spenden Sie oder nutzen Sie LEO Pur!

 
  •  
  • Betreff

    Methodenaufruf

    Quellen

    Der Fokus der Integration dieses Service Drops liegt auf der Überprüfung der Serviceschnittstellen, wie z.B. die korrekten Methodenaufrufe im Integration Framework wie der Middleware.

    Kommentar

    Aus einem Entwurf für die Softwarearchitektur einer Cloud. Ich bin leider IT-mäßig ein völlig unbeschriebenes Blatt und bin weder inhaltlich noch terminologisch sattelfest.


    Könnt ihr mir helfen? Die "Methodenaufrufe" verstehe ich schlicht nicht, beim Rest des Satzes bin ich vor allem stilistisch und terminologisch unsicher, wie man es im Englischen IT-Jargon ausdrücken würde (bilde mir aber ein, dass ich zumindest kapiere, was gemeint ist 😉 ).


    -> Ich freue mich über jede Erklärung und jeden Übersetzungsvorschlag!

    VerfasserMeiki_zett (1087548) 18 Jun. 21, 10:06
    Vorschlagmethod call
    Kommentar

    Das ist der Aufruf eines Unterprogramms.

    #1Verfasser eineing (771776) 18 Jun. 21, 10:32
    Kommentar

    In a couple of computer languages, some functions (repeatable pieces of code) are called methods. In German-It the term has been adopted, and the word "Methoden" is used.


    A "Drop" is the name for the set of code about to go into a different phase of the development cycle, e.g. into the testing phase or into production.


    A Framework is literally, a technical Gerüst. It contains how you report errors, how you log performance, how you call "Methods" etc. Basically all the stuff that you have to do over and over, regardless which parts of the code are being used.


    An Intergration Framework is a particular framework that deals (most likely) with the integration between systems. It could have other uses, without context hard to say, but the term is usually used when dealing with other systems.


    Middleware is a term for software that is definitely not front end software like HTML. It's usually used to transport data from the front end to the back end (database) or other systems and does not store the data itself.


    Putting it all together:


    The main focus of this service drop is checking the service interfaces, for example, the correct method calls in the integration framework of the middleware.



    #2Verfasser HappyMan (911136) 18 Jun. 21, 10:39
    Kommentar

    DANKE! You enlightened me, HappyMan ;) I much appreciate your detailed explanations!


    #3VerfasserMeiki_zett (1087548) 22 Jun. 21, 10:02
    Kommentar

    The "wie der Middleware" bit is a bit horrible.

    #4Verfasser RTH01 (932829) 22 Jun. 21, 10:16
    Kommentar

    Weil ein "oder" vor dem zweiten "wie" fehlt? Ich denke der Autor sieht eher die Middleware als Integration Framework an, dann stimmt das schon so und bezieht sich korrekt, es wäre nur stilistisch besser gewesen, die Wiederholung zu vermeiden und eine andere Methode der Bespieleinleitung zu wählen.


    Ich mache mir eher Gedanken darüber, dass beim ersten "wie" der Fall dessen übernommen werden müsste, auf das sich das Beispiel bezieht, also ein "... Überprüfung der Schnittstellen (Genitiv) wie z.B. der korrekten Methodenaufrufe (ebenfalls Genitiv, ist ja schließlich eine Schnittstelle und keine Überprüfung)... "


    Übrigens @HappyMan: Ich weiß dies ist kein Technikforum sondern ein Sprachforum, wenn man aber schon solche Erläuterungen loslässt sollte man trotzdem präzise sein.

    HTML ist keine Software, sondern eine "Datenbeschreibungssprache", in der man Texte niederlegt, so dass sie von einem z.B. Webbrowser interpretiert werden können und dieser dann Texte und Links darstellen kann.

    Ein Framework kann zwar auch aus reinen Spezifikationen bestehen (insofern ist " 'Gerüst', ... how you report errors" nicht ganz falsch), als Integration Framework ist es aber selbst Software, die Routinen anbietet, um verschiedene Module in einem System einbinden zu können. Es beschreibt also nicht mehr, z.B. wie man Fehler loggt, sondern loggt sie selber, wenn das zu integrierende Modul die entsprechende Methode aufruft.

    Und Middleware muss nicht unbedingt mit einem Frontend verknüpft sein, sondern verknüpft üblicherweise Schnittstellenbefehle in einem Gerät (device) mit der meist in Maschinencode hinterlegten Firmware. So auf Anhieb fällt mir kein Anwendungsfall ein, bei der Middleware (sofern der Begriff auch korrekt verwendet wird) direkt eine Frontend-Anbindung hat, eher kommuniziert sie mit einem Client, der seinerseits wieder aus Schnittstellenteil und Frontend besteht.

    #5Verfasserm.dietz (780138)  23 Jun. 21, 13:58
    Kommentar

    @m.dietz


    Obviously my intent was to explain thing to a layperson in terms that they may have heard or understand. I find your comment quite snarky in that regard and also inaccurate.


    HTML ist keine Software, sondern eine "Datenbeschreibungssprache", in der man Texte niederlegt, so dass sie von einem z.B. Webbrowser interpretiert werden können und dieser dann Texte und Links darstellen kann.


    If I had said "...that is definitely not (part of the) front end software like HTML" then there'd be no problem. Did it make a difference to anyone reading it, I doubt it very much. Snark 1.


    Ein Framework kann zwar auch aus reinen Spezifikationen bestehen (insofern ist " 'Gerüst', ... how you report errors" nicht ganz falsch),


    Yes there are document frameworks, also testing frameworks and god knows whatever else for frameworks. But if you ask practically anyone in IT, without context, what a framework is, and they will give the same answer as me, because that is the framework that software professionals encounter by far the most often. It's like me saying "Dackel" and you countering, "ahh you have to be precise because there are Rauhaardackel as well". Your addition adds nothing to the explanation because we are obviously talking about a software framework in the quote below. You are taking my answer completely out of context, as if I'm explaining what 'framework' could mean, instead of answering what it probably means in this context. Calling that imprecise is Snark 2.


    als Integration Framework ist es aber selbst Software, die Routinen anbietet, um verschiedene Module in einem System einbinden zu können. Es beschreibt also nicht mehr, z.B. wie man Fehler loggt, sondern loggt sie selber, wenn das zu integrierende Modul die entsprechende Methode aufruft.


    Integration Framework is the washiest term of all these and without the original document it is impossible to say what this thing does, that's why I wrote "most likely" and "could have other uses". I've encountered people calling their system testing environment where several independently developed systems come together, in particular their entry points to the environment, an integration framework i.e. completely devoid of software. It is therefore completely imprecise of you to claim that an integration framework is something universally acknowledged as meaning something particular or even being software. Silly snark 3.


    Und Middleware muss nicht unbedingt mit einem Frontend verknüpft sein, sondern verknüpft üblicherweise Schnittstellenbefehle in einem Gerät (device) mit der meist in Maschinencode hinterlegten Firmware. So auf Anhieb fällt mir kein Anwendungsfall ein, bei der Middleware (sofern der Begriff auch korrekt verwendet wird) direkt eine Frontend-Anbindung hat, eher kommuniziert sie mit einem Client, der seinerseits wieder aus Schnittstellenteil und Frontend besteht.


    I did not say that it must be connected to frontend. I literally used the word "usually". Again you take things completely out of context. I was trying, successfully given Meiki's reaction, to give an idea about what he/she was working with. I was not trying to be some smartarse and list all possible contexts where middleware could be used, between which components it could be used and whether it's a bought black-box software solution or a self-developed piece of code, or whether it's running directly on portable hardware, it's client code is running on the portable hardware or whether the entire thing is running on the backend or a thousand other variations.


    Overall I find it highly aggravating for my post to be labelled "imprecise" by someone who I severely doubt has 30+ years in the IT industry, in particular backend system development where these terms are used daily, like me. The only thing in my post that is imprecise, is that I left "part of the" out in snark 1. But even then, jeez, did it matter?







    #6Verfasser HappyMan (911136)  23 Jun. 21, 15:30
    Kommentar

    In defence of m.dietz, and speaking as someone who does have 30+ years experience in the IT industry, I was also somewhat unhappy about the phrase "front end software like HTML" (and I don't think writing "part of the front end software like HTML" helps much either) but I didn't have the patience earlier to write anything about it.


    If I may offer an observation: if one finds a post 'snarky', it doesn't make it any better to come back with an even 'snarkier' post.


    I agree that m.dietz's post didn't really add anything that helps in the context of this particular OP, but posts of clarification may well be useful when other readers come along in the future, and even Meiki_zett might win something from m.dietz's clarifications as to the usual or other possible uses of the terminology in question.

    #7Verfasser amw (532814)  23 Jun. 21, 16:42
    Kommentar

    @amw, I think in perhaps any other topic I wouldn't have answered so snarky, but backend system development has been my bread and butter for thirty years, a bit of professional pride got the better of me. I will try to follow your advice though.

    #8Verfasser HappyMan (911136) 23 Jun. 21, 16:53
    Kommentar

    #5 Ich habe den letzen Teil das Satzes als "im Integration Framework wie [in] der Middleware" gelesen, aber vielleicht war er gar nicht so gemeint.

    #9Verfasser RTH01 (932829) 24 Jun. 21, 00:14
    Kommentar

    No insult meant, but I too am in that business for more than 30 years now, although I'm more an expert in frontend development and interface transition. I also know a bit more about how deeply to go when explaining technical issues for laymen and even here, you were much too detailed for a layman to understand. Anyway, I have to deal constantly with laymen using technical terminology the wrong way, so that's why even when simplifying facts for laymen, I don't want to support explaining things wrong. Experts may know what the correct words are, laymen don't!


    I also asked you to be precise, especially because it was an unrequested clarification of technical terminology, which (additionally) did not clarify anything about why you chose exactly that translation proposal. This kind of "clarification" always has the stench of showing-off. And if it then is even wrong (e.g. the description of HTML as frontend software, and no, HTML is not even part of the front end software like electrical currents are not part of measurement software) or misleading(e.g. speaking about document frameworks and specifications when the precise integration framework was meant), this adds the stench of a gasbag on top.

    #10Verfasserm.dietz (780138) 24 Jun. 21, 10:58
    Kommentar

    I also know a bit more about how deeply to go when explaining technical issues for laymen and even here, you were much too detailed for a layman to understand.


    Got to laugh at that sentence. I pick just the key words out of the OP's sentence and use one or two sentences for each term and a maximum of 35 words per term and that's "too detailed" for you? And then you write a whole jumbled paragraph on middleware, because you know how deeply to go to laymen? Right, buddy.


    Congrats, you picked up on HTML not being software. However, I'll leave it to you to correct the mistakes I found in your stuff as it seems to be important to you that the terms are used precisely and correctly. No insult meant, of course.

    #11Verfasser HappyMan (911136)  24 Jun. 21, 12:55
    Kommentar

    No, I did not write my pargraph on middleware for laymen, I wrote it FOR YOU! FOR AN EXPERT WHO SHOULD KNOW IT BETTER THAN CLAIMING SUCH A NONSENSE!!!


    But regarding your reaction on my critic I have to even doubt that you are old enough to have 30+ years of professional knowledge in any field.



    #12Verfasserm.dietz (780138)  24 Jun. 21, 13:03
    Kommentar

    Got it dude. You wrote something inaccurate for me, but that's ok, because my (slightly) inaccurate statement regarding HTML was an unforgivable sin in your eyes.


    Anyhow, I'm done with arguing as it's probably annoying for other people. Especially now that we've reached the capital letters stage of our argument. Lol. Whatever you write in this thread I not respond to. I hope in the future, that we can combine to help other people, instead of taking shots at each other.

    #13Verfasser HappyMan (911136) 24 Jun. 21, 13:34
     
  •  
  •  
  •  
  •  
  •  
  
 
 
 
 
  automatisch zu   umgewandelt