• Jaloopa (unregistered)
    private static string frist = "frist";
    private static @string Frist = "frist";
    private static string2 _frist = "frist";
  • TheCPUWizard (unregistered)

    So many have forgotten (or ignored, or been ignorant of) the fundamental difference in intent....

    "OA" = Object Access - dealing with things that exist on a different systems; controlling and examining them.

    "ST" = "State Transfer". NOT dealing with the remote. More interesting si that Transfer is "move from one place to another." - NOT really COPY (that is duplicate).. So if I transfer from the "A train" to the "B train" I am no longer on the "A train at all". I have moved. Thus it *should be for the official location of definitive state. Of course this was heard, so people just allowed state to be represented in multiple locations typically without monotonic, atomic, ownership. - leading us back to "Button button how has the button".

  • WTFGuy (unregistered)
    Comment held for moderation.
  • pudin9 (unregistered)
    Comment held for moderation.
  • Zed (unregistered)

    What's the wtf? Credentials are hard coded

  • (nodebb)

    MS should have never introduced the naming @ construct - I never used it in two decades, I'm all for options, but using keywords for other purposes than what they are intended for seems just wrong, even today.

  • (nodebb)

    I'm impressed. They managed to create a type system worse than gRPC's.

  • Wizofaus (unregistered) in reply to MaxiTB
    Comment held for moderation.
  • (nodebb)

    What's fun is that when implemented with discipline, particularly an eye to Doing Things As Correctly As Possible, then SOAP can be a nice thing to work with.

  • NathanAnymn (unregistered)
    Comment held for moderation.
  • nz (unregistered) in reply to MaxiTB

    I guess it's there for language interop, so that C# can use classes and methods written in other languages even if their names happen to match some C# keyword.

    Oh, and can't "other language" be "an older C# version where that wasn't a keyword yet"?

  • (nodebb)

    The history of SOAP: What Microsoft creates, so shall Microsoft take away.

Leave a comment on “An Accountable Service”

Log In or post as a guest

Replying to comment #:

« Return to Article