분석설계&모델링전문가교육내용정리 › JWSDP › 삽질 › lighttpd › http response code › Language
- 마크업언어의역사 . . . . 4 matches
[GML] : General [Markup Language] 의 약자로 1979년 Dr. GoldFarb가 법률문서관리위해 최초 개발
[SGML] : Standard Generalized Markup Language, 미국 및 캐나다에서 공공문서나 법률문서관리목적 또는 출판업계에서 사용목적으로 많이 사용, 규칙이 너무 복잡 HTML과 XML의 모태
[HTML] : Hyper-Text Markup Language, 1991 Tim Berners Lee가 개발, 단순함, 인터넷상에서 쉽게 사용가능한 마크업언어, 인터넷 일반화에 큰 영향
[XML] : eXtensible Markup Language, 플랫폼 독립적, 이기종간 정보교환가능, 데이터 구조 정의에 적합, SGML의 강력함, HTML의 쉽고 가벼움을 가진 실용적특성을가지고 SGML을 재정의 - 코틀린마이크로서비스개발-후안안토니오 . . . . 3 matches
- Ubiquitous Language: 개발자와 사용자간의 공통적이고 엄격한 언어를 구축해야한다. 이 언어는 도메인 모델에 기초해야하며, 도메인 전문가와 공통적이고 유동적인 대화를 하는데 도움이된다.
- Ubiquitous Language: Microservices가 사용하는 언어가 유비쿼터스 언어임을 보장해야하므로 노출된 Operation과 Interface는 Context Domain Language로 표현된다. - BuildingMicroservices;마이크로서비스아키텍처구축-샘뉴먼지음,정성권옮김 . . . . 2 matches
- JSON : HATEOAS를 위해 HAL 적용 (Hypertext Application Language)
- HAL(Hypertext Application Language), HAL Browser - XML . . . . 2 matches
eXtensible [Markup Language]
WML(Wireless Markup Language) - IDL . . . . 1 match
Interface Definition Language - IT개발 . . . . 1 match
[Language] - IT관련 . . . . 1 match
[모바일], [eMail], [Web], MoniWiki, [공개S/W], [SSH], [Language], [OS] - Markdown . . . . 1 match
[["Markup Language"]] - MoniWikiPo . . . . 1 match
"Language-Team: ko <ko@li.org>\n" - OGNL . . . . 1 match
Oject Graph Navigation Language - OurSoftwareDependencyProblem . . . . 1 match
My own background includes a decade of working with Google’s internal source code system, which treats software dependencies as a first-class concept,1 and also developing support for dependencies in the Go programming language.2
Dependency managers now exist for essentially every programming language. Maven Central (Java), Nuget (.NET), Packagist (PHP), PyPI (Python), and RubyGems (Ruby) each host over 100,000 packages. The arrival of this kind of fine-grained, widespread software reuse is one of the most consequential shifts in software development over the past two decades. And if we’re not more careful, it will lead to serious problems.
Develop your own systematic ways to check code quality. For example, something as simple as compiling a C or C++ program with important compiler warnings enabled (for example, -Wall) can give you a sense of how seriously the developers work to avoid various undefined behaviors. Recent languages like Go, Rust, and Swift use an unsafe keyword to mark code that violates the type system; look to see how much unsafe code there is. More advanced semantic tools like Infer7 or SpotBugs8 are helpful too. Linters are less helpful: you should ignore rote suggestions about topics like brace style and focus instead on semantic problems.
Even with these examples and other off-the-shelf options, run-time isolation of suspect code is still too difficult and rarely done. True isolation would require a completely memory-safe language, with no escape hatch into untyped code. That’s challenging not just in entirely unsafe languages like C and C++ but also in languages that provide restricted unsafe operations, like Java when including JNI, or like Go, Rust, and Swift when including their “unsafe” features. Even in a memory-safe language like JavaScript, code often has access to far more than it needs. In November 2018, the latest version of the NPM package event-stream, which provided a functional streaming API for JavaScript events, was discovered to contain obfuscated malicious code that had been added two and a half months earlier. The code, which harvested large Bitcoin wallets from users of the Copay mobile app, was accessing system resources entirely unrelated to processing event streams.18 One of many possible defenses to this kind of problem would be to better restrict what dependencies can access.
Equifax’s experience drives home the point that although dependency managers know the versions they are using at build time, you need other arrangements to track that information through your production deployment process. For the Go language, we are experimenting with automatically including a version manifest in every binary, so that deployment processes can scan binaries for dependencies that need upgrading. Go also makes that information available at run-time, so that servers can consult databases of known bugs and self-report to monitoring software when they are in need of upgrades.
Creeping dependencies can also affect the size of your project. During the development of Google’s Sawzall23—a JIT’ed logs processing language—the authors discovered at various times that the main interpreter binary contained not just Sawzall’s JIT but also (unused) PostScript, Python, and JavaScript interpreters. Each time, the culprit turned out to be unused dependencies declared by some library Sawzall did depend on, combined with the fact that Google’s build system eliminated any manual effort needed to start using a new dependency.. This kind of error is the reason that the Go language makes importing an unused package a compile-time error.
Develop better dependency technology for tomorrow. Dependency managers have essentially eliminated the cost of downloading and installing a dependency. Future development effort should focus on reducing the cost of the kind of evaluation and maintenance necessary to use a dependency. For example, package discovery sites might work to find more ways to allow developers to share their findings. Build tools should, at the least, make it easy to run a package’s own tests. More aggressively, build tools and package management systems could also work together to allow package authors to test new changes against all public clients of their APIs. Languages should also provide easy ways to isolate a suspect package. - Spring3.0특징요약 . . . . 1 match
=== Spring Expression Language === - UML에대한이해 . . . . 1 match
== UML(Unified Modeling Language)이란 == - WSDL . . . . 1 match
WSDL(Web Service Description Language)는 [웹서비스]를 사용하기 위한 기술적 구문을 나타내기 위해 제안된 표준으로 2000년 9월 IBM, MS등의 회사가 W3C에 표준화 대상으로 제출함 - WebUploadStreamFormat . . . . 1 match
Accept-Language: ko - WikiSandBox . . . . 1 match
== PhpLanguage == - dojo . . . . 1 match
Dojo 는 JavaScript와 Dynamic Hypertext Markup Language (DHTML) 커뮤니티를 표준 JavaScript 라이브러리를 구현하여 일관된 방향으로 통합하기 위해 설계된 커뮤니티 프로젝트이다. 이 커뮤니티는 함께 일하는 사람들 없이는 성공할 수 없다는 것을 깨달았기 때문에 세 개의 이전 툴킷들을 통합하여 Dojo Foundation을 만들었다. 여기에서 코드를 소유 및 관리한다. Dojo는 Ajax 에디션, I/O 에디션 "Kitchen Sink"에디션 같은 여러 옵션 패키지들을 갖고 있다. 여기에는 전체 툴 세트가 포함된다. - jEdit . . . . 1 match
SuperScript.lastLanguage=javascript - json . . . . 1 match
JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999. JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language. - ruby . . . . 1 match
ProgramLanguage - wsdl . . . . 1 match
WSDL(Web Service Description Language)는 [웹서비스]를 사용하기 위한 기술적 구문을 나타내기 위해 제안된 표준으로 2000년 9월 IBM, MS등의 회사가 W3C에 표준화 대상으로 제출함 - xpath . . . . 1 match
XPath(XML Path Language) - XML 문서의 표준경로 지정 언어 - 마크업언어 . . . . 1 match
[Markup Language]
