約 4,531,030 件
https://w.atwiki.jp/natsutan/pages/70.html
概要 inlude "tclInt.h" 変数宣言 /* * The data structure below is used to report background errors. One such * structure is allocated for each error; it holds information about the * interpreter and the error until an idle handler command can be invoked. */ typedef struct BgError { [[Tcl_Obj]] *errorMsg;/* Copy of the error message (the interp's * result when the error occurred). */ Tcl_Obj *returnOpts;/* Active return options when the error * occurred */ struct BgError *nextPtr;/* Next in list of all pending error reports * for this interpreter, or NULL for end of * list. */ } BgError; /* * One of the structures below is associated with the "tclBgError" assoc data * for each interpreter. It keeps track of the head and tail of the list of * pending background errors for the interpreter. */ typedef struct ErrAssocData { [[Tcl_Interp]] *interp;/* Interpreter in which error occurred. */ Tcl_Obj *cmdPrefix;/* First word(s) of the handler command */ BgError *firstBgPtr;/* First in list of all background errors * waiting to be processed for this * interpreter (NULL if none). */ BgError *lastBgPtr;/* Last in list of all background errors * waiting to be processed for this * interpreter (NULL if none). */ } ErrAssocData; /* * For each exit handler created with a call to Tcl_Create(Late)ExitHandler there is * a structure of the following type */ typedef struct ExitHandler { Tcl_ExitProc *proc;/* Function to call when process exits. */ [[ClientData]] clientData;/* One word of information to pass to proc. */ struct ExitHandler *nextPtr;/* Next in list of all exit handlers for this * application, or NULL for end of list. */ } ExitHandler; /* * There is both per-process and per-thread exit handlers. The first list is * controlled by a mutex. The other is in thread local storage. */ static ExitHandler *firstExitPtr = NULL; /* First in list of all exit handlers for * application. */ static ExitHandler *firstLateExitPtr = NULL; /* First in list of all late exit handlers for * application. */ TCL_DECLARE_MUTEX(exitMutex) /* * This variable is set to 1 when Tcl_Finalize is called, and at the end of * its work, it is reset to 0. The variable is checked by TclInExit() to allow * different behavior for exit-time processing, e.g. in closing of files and * pipes. */ static int inFinalize = 0; static int subsystemsInitialized = 0; /* * This variable contains the application wide exit handler. It will be * called by Tcl_Exit instead of the C-runtime exit if this variable is set * to a non-NULL value. */ static Tcl_ExitProc *appExitPtr = NULL; typedef struct ThreadSpecificData { ExitHandler *firstExitPtr;/* First in list of all exit handlers for this * thread. */ int inExit;/* True when this thread is exiting. This is * used as a hack to decide to close the * standard channels. */ } ThreadSpecificData; static Tcl_ThreadDataKey dataKey; #ifdef TCL_THREADS typedef struct { Tcl_ThreadCreateProc *proc;/* Main() function of the thread */ ClientData clientData;/* The one argument to Main() */ } ThreadClientData; static Tcl_ThreadCreateType NewThreadProc(ClientData clientData); #endif /* TCL_THREADS */ 関数 BgErrorDeleteProc HandleBgErrors VwaitVarProc Tcl_BackgroundError TclBackgroundException HandleBgErrors TclDefaultBgErrorHandlerObjCmd TclSetBgErrorHandler TclGetBgErrorHandler BgErrorDeleteProc TclCreateLateExitHandler Tcl_DeleteExitHandler TclDeleteLateExitHandler Tcl_CreateThreadExitHandler Tcl_DeleteThreadExitHandler Tcl_SetExitProc Tcl_Exit TclInitSubsystems Tcl_Finalize Tcl_FinalizeThread TclInExit TclInThreadExit Tcl_VwaitObjCmd Tcl_UpdateObjCmd NewThreadProc Tcl_CreateThread
https://w.atwiki.jp/mrfrtech/pages/70.html
Market Highlights Cloud database is a database service which can be used in storing and managing files through the cloud. Enterprises can host databases on the cloud without access to hardware. The ability to scale business at a rapid pace using cloud is likely to lead to its adoption by businesses of all sizes. The global Cloud Database Market Growth report compiled by Market Research Future (MRFR) evaluates various growth opportunities and trends amid the COVID-19 pandemic and changes in business models for the period of 2020 to 2027 (forecast period). Market Scope The global cloud database market is expected to reach USD 21.66 billion growing at 46.78% CAGR over the forecast period. The advent of internet of things (IoT) and rise of cloud computing are major drivers of the market. Implementation of cloud databases for improving service, lowering cost, and expediting services can benefit the market. Rise in digitization of data and the move towards cloud by organizations of all sizes can be a golden opportunity for cloud database providers. Request a Free Sample @ https //www.marketresearchfuture.com/sample_request/6847 Rise of application development and mass computing can drive the adoption of cloud databases by organizations making it easier for app developers in storing, migrating, and sharing data. The virtual nature of cloud databases allow it to recover from crashes and failures in programs quicker and the disposability nature can drive the market demand in the global cloud database market. It can cover machines and entire data centers. But concerns of data security can impede market growth. Competitive Outlook SAP AG, CenturyLink, CSC (Computer Science Corporation), Salesforce.com Inc., Google Inc., Oracle, Amazon.com, Rackspace Inc., IBM, and Microsoft are key players in the global cloud database market. Segmentation By database, the cloud database market is divided into SQL database and NoSQL database. By model, this market is segmented into service model and deployment model. By service model, the market is further segmented into private cloud, virtual private cloud, public cloud, and hybrid cloud. Deployment model segmentations include infrastructure as a service (IaaS), database as a service (DBaaS), and platform as a service (PaaS). By deployment model, the DBaaS segment can provide security to data with tight surveillance and software upgrades designed to maintain the integrity of data stored in the database. By component, the market is segmented into software and service. By software the market is segmented into database application builder, database encryption, data scaling and replication, backup and recovery, and others. By service, the market is segmented into training and consulting service, system and network integration service, and deployment and maintenance service. By organization size, the market is segmented into large enterprise and small and medium-sized enterprise. By end-user, the market is segmented into academic, BFSI, healthcare, IT and telecom, government, and others. Regional Analysis The regional analysis of cloud database market is considered for North America, Europe, Asia-Pacific, and the rest of the world. Implementation of IoT and increasing adoption of cloud-based services in North American countries such as the US and Canada is expected to dominate the cloud database market during the assessment period. Several investments and research and developments are taking place in the US owing to the increasing need for cloud database by the IT companies. This in turn ensures an enhanced cloud infrastructure coupled with the provision of network security for the cloud database users. Increase in the adoption of security based applications in Asia-Pacific is expected to enhance the cloud database market. Hence, Asia-Pacific is expected to be the fastest growing region in the market during the forecast period. Europe is expected to witness a significant growth in the market owing to the growing need for managed database solutions from the prominent IT companies investing in the European markets. Brows Full Report @ https //www.marketresearchfuture.com/reports/cloud-database-market-6847 Table of Contents 1 Executive Summary 2 Scope of The Report 2.1 Market Definition 2.2 Scope of The Study 2.2.1 Research Objectives 2.2.2 Assumptions Limitations 2.3 Market Structure Continued… Similar Report** B2B Telecommunication Market Information by Solution (Unified Communication and Collaboration), Deployment (Fixed, Mobile), Organization Size (Large, Enterprise), Application (Industrial, Commercial) and regions Trending #MRFR Report** https //ictmrfr.blogspot.com/2022/04/geofencing-market-companies-growth-with.html https //blogfreely.net/pranali004/telecom-expense-management-market-size-impressive-cagr-changing-business-scope https //postheaven.net/pranali004/financial-app-industry-impressive-cagr-changing-business-needs-scope-of https //market-research-future.tribe.so/post/openstack-service-market-research-impressive-cagr-changing-scope-of-current--6263de46791566c10c79891e https //www.scutify.com/articles/2022-04-24-infrastructure-as-a-service-industry-cagr-changing-business-scope-of-current-and-future-industry- About Market Research Future At Market Research Future (MRFR), we enable our customers to unravel the complexity of various industries through our Cooked Research Report (CRR), Half-Cooked Research Reports (HCRR), Raw Research Reports (3R), Continuous-Feed Research (CFR), and Market Research Consulting Services. Contact Market Research Future (Part of Wantstats Research and Media Private Limited) 99 Hudson Street, 5Th Floor New York, NY 10013 United States of America 1 628 258 0071 (US) 44 2035 002 764 (UK) Email sales@marketresearchfuture.com Website https //www.marketresearchfuture.com
https://w.atwiki.jp/satoschi/pages/562.html
Ladino【lad】 ラディノ語 00 Indo-European 01 Italic 02 Romance 03 Italo-Western 04 Western 05 Gallo-Iberian 06 Ibero-Romance 07 West Iberian 08 Castilian Cyrillic script【Cyrl】 Hebrew script【Hebr】 Latin script【Latn】 《現》living language アメリカ合衆国【US】 アルジェリア【DZ】 アルバニア【AL】 イスラエル【IL】 ギリシャ【GR】 クロアチア【HR】 セルビア【RS】 トルコ【TR】 ブルガリア【BG】 プエルトリコ【PR】 ボスニア・ヘルツェゴビナ【BA】 マケドニア旧ユーゴスラビア共和国【MK】 モロッコ【MA】 ルーマニア【RO】 言語名別称 alternate names Dzhudezmo ジュデズモ語 Haketia Hakitia Haquetiya Judeo Spanish (Judeo-Spanish, Judaeo-Spanish, Judæo-Spanish) ユダヤ＝スペイン語 Judezmo Sefardi Sephardic Spanyol ラジノ語 ラディン語 ラディーノ語 方言名 dialect names Haquetiya (Haketia, Haketiya, Hakitia) Judezmo (Jidyo, Judyo) Ladino 表記法 writing Cyrillic script【Cyrl?】 Hebrew script【Hebr?】 Latin script【Latn】 参考文献 references WEB ISO 639-3 Registration Authority - SIL International LINGUIST List Ethnologue Wikipedia ウィキペディア
https://w.atwiki.jp/seko/pages/280.html
日本語の文字化け WristPDAには英語版のPalmDesktopが付属しています。 これをそのまま使用する場合、インストーラーでインストールできるため一番簡単です。 ただしそのままでは当然日本語が使用できません。 このように日本語が文字化けしてしまいます。 しかし、Windowsのレジストリを編集することによって日本語を表示させることができます。 ただし、完全な日本語化ではありませんのでメニューは英文のままです。 さらにタイトルバーなど一部に文字化けが残ります。 また、レジストリはWindowsシステムの重要な情報を管理しているため間違った修正をすると最悪Windowsが起動しなくなるなど深刻な障害が発生します。くれぐれも自己責任で行ってください。 WristPDA付属のPalmDesktopのインストール ここをクリックすると拡大します WristPDA付属のCD-ROMをPCのCD-ROMドライブにセットします。 自動的にインストーラーが起動しますので、言語を選択します。当然日本語はありませんので English を選択します。 ここをクリックすると拡大します WristPDA Softwareを選択します。 ここをクリックすると拡大します インストーラーが起動してインストールがはじまります。 ここをクリックすると拡大します ここをクリックすると拡大します Palm Desktopを使用する場合、Palm Desktopにチェックを入れ、Nextボタンをクリックします。 ここをクリックすると拡大します 同期させるWristPDAのユーザー名を決め、新規ユーザー名の登録をします。 ここをクリックすると拡大します ここをクリックすると拡大します インストールが完了したら、WristPDAとPCを付属のUSBケーブルで接続し、ホットシンクを実行します。正しくホットシンクできればインストールは完了です。 ホットシンクの方法についてはアプリケーションのインストールを参照してください。 レジストリを編集して日本語を表示する方法については レジストリを編集して日本語を表示する を参照してください。 免責事項 当サイトの内容によって被る損害についてサイト管理者は一切責任を持ちません。自己責任の上で情報を活用してください。 記載されている製品名等は各社の登録商標あるいは商標です。 一部引用画像は引用元に著作権があります。 当サイトの内容、写真等に問題がある場合、info ＠ pamupamu.com までご連絡ください。できる限りすみやかに対処いたします。 説明の便宜上直接リンクがはられている場合があります。不具合がありましたらご連絡ください。 Copyright (C) 2006 by Shigeyuki Seko all right reserved.
https://w.atwiki.jp/usb_audio/pages/27.html
原文：Audio Terminal Types 1.0(PDF) USB Device Class Definition for Terminal Types Release 1.0 March 18, 1998 6 1 Introduction The intention of this document is to describe in detail all the Terminal Types that are supported by the Audio Device Class. This document is considered an integral part of the Audio Device Class Specification, although subsequent revisions of this document are independent of the revision evolution of the main Audio Device Class Specification. This is to easily accommodate the addition of new Terminal Types without impeding the core Audio Device Class Specification. 1.1 Scope The Audio Device Class Definition applies to all devices or functions embedded in composite devices. All audio signals inside an audio function start at an Input Terminal, pass through some Units, and leave the function through an Output Terminal. Units can manipulate the signal in various ways. Terminals represent the connections of the function to the outside world. As part of the Terminal descriptor, the wTerminalType field specifies the vendor’s suggested use of the Terminal. For example, a pair of speakers is a more suitable target for music output than a telephone line. This feature allows a vendor to ensure that applications use the device in a consistent and meaningful way. 1.2 Related Documents · Universal Serial Bus Specification, 1.0 final draft revision (also referred to as the USB Specification). In particular, see Chapter 9, “USB Device Framework”. · Universal Serial Bus Device Class Definition for Audio Data Formats (referred to in this document as USB Audio Data Formats). · Universal Serial Bus Device Class Definition for Terminal Types (referred to in this document as USB Audio Terminal Types). · ANSI S1.11-1986 standard. · MPEG-1 standard ISO/IEC 111172-3 1993. · MPEG-2 standard ISO/IEC 13818-3 Feb. 20, 1997. · Digital Audio Compression Standard (AC-3), ATSC A/52 Dec. 20, 1995. (available from http //www.atsc.org) · ANSI/IEEE-754 floating-point standard. · ISO/IEC 958 International Standard Digital Audio Interface and Annexes. · ISO/IEC 1937 standard. · ITU G.711 standard. 1.3 Terms and Abbreviations None. USB Device Class Definition for Terminal Types Release 1.0 March 18, 1998 7 2 Terminal Types The following is a list of possible Terminal Types. This list is non-exhaustive and will only be expandedin the future. 2.1 USB Terminal Types These Terminal Types describe Terminals that handle signals carried over the USB, usually throughisochronous pipes. These Terminal Types are valid for both Input and Output Terminals. Table 2-1 USB Terminal Types Terminal Type Code I/O Description USB Undefined 0x0100 I/O USB Terminal, undefined Type. USB streaming 0x0101 I/O A Terminal dealing with a signal carried over an endpoint in an AudioStreaming interface. The AudioStreaming interface descriptor points to the associated Terminal through the bTerminalLink field. USB vendor specific 0x01FF I/O A Terminal dealing with a signal carried over a vendor-specific interface. The vendor-specific interface descriptor must contain a field that references the Terminal. 2.2 Input Terminal Types These Terminal Types describe Terminals that are designed to record sounds. They either are physically part of the audio function or can be assumed to be connected to it in normal operation. These Terminal Types are valid only for Input Terminals Table 2-2 Input Terminal Types Termina Type Code I/O Description Input Undefined 0x0200 I Input Terminal, undefined Type. Microphone 0x0201 I A generic microphone that does not fit under any of the other classifications. Desktop microphone 0x0202 I A microphone normally placed on the desktop or integrated into the monitor. Personal microphone 0x0203 I A head-mounted or clip-on microphone. Omni-directional microphone 0x0204 I A microphone designed to pick up voice from more than one speaker at relatively long ranges. Microphone array 0x0205 I An array of microphones designed for directional processing using host-based signal processing algorithms. USB Device Class Definition for Terminal Types Release 1.0 March 18, 1998 8 Terminal Type Code I/O Description Processing microphone array 0x0206 I An array of microphones with an embedded signal processor. 2.3 Output Terminal Types These Terminal Types describe Terminals that produce audible signals that are intended to be heard by the user of the audio function. They either are physically part of the audio function or can be assumed to be connected to it in normal operation. These Terminal Types are only valid for Output Terminals. The distinction between headphones, desktop speakers, and room speakers may be used by applications to select different 3D signal processing algorithms. Table 2-3 Output Terminal Types Terminal Type Code I/O Description Output Undefined 0x0300 O Output Terminal, undefined Type. Speaker 0x0301 O A generic speaker or set of speakers that does not fit under any of the other classifications. Headphones 0x0302 O A head-mounted audio output device. Head Mounted Display Audio 0x0303 O The audio part of a VR head mounted display. The Associated Interfaces descriptor can be used to reference the HID interface used to report the position and orientation of the HMD. Desktop speaker 0x0304 O Relatively small speaker or set of speakers normally placed on the desktop or integrated into the monitor. These speakers are close to the user and have limited stereo separation. Room speaker 0x0305 O Larger speaker or set of speakers that are heard well anywhere in the room. Communication speaker 0x0306 O Speaker or set of speakers designed for voice communication. Low frequency effects speaker 0x0307 O Speaker designed for low frequencies (subwoofer). Not capable of reproducing speech or music. 2.4 Bi-directional Terminal Types These Terminal Types describe an Input and an Output Terminal for voice communication that are closely related. They should be used together for bi-directional voice communication. They may be used separately for input only or output only. These types require two Terminal descriptors. Both have the same type. The two Terminals are linked together through the bAssocTerminal fields in their respective Terminal descriptors. The Associated Interfaces descriptor can be used to reference a HID interface for conferencing functions. USB Device Class Definition for Terminal Types Release 1.0 March 18, 1998 9 Table 2-4 Bi-directional Terminal Types Terminal Type Code I/O Description Bi-directional Undefined 0x0400 I/O Bi-directional Terminal, undefined Type. Handset 0x0401 I/O Hand-held bi-directional audio device. Headset 0x0402 I/O Head-mounted bi-directional audio device. Speakerphone, no echo reduction 0x0403 I/O A hands-free audio device designed for host-based echo cancellation. Echo-suppressing speakerphone 0x0404 I/O A hands-free audio device with echo suppression capable of half-duplexoperation. Echo-canceling speakerphone 0x0405 I/O A hands-free audio device with echo cancellation capable of full-duplex operation. 2.5 Telephony Terminal Types These Terminal Types describe Terminals that connect to the PSTN or PBX. Initiating calls and monitoring call progress will be done through an associated interface which may be Communication, HID or Vendor-Specific class. These Terminals are bi-directional and follow the rules for bi-directional Terminals. Table 2-5 Telephony Terminal Types Terminal Type Code I/O Description Telephony Undefined 0x0500 I/O Telephony Terminal, undefined Type. Phone line 0x0501 I/O May be an analog telephone line jack, an ISDN line, a proprietary PBX interface, or a wireless link. Telephone 0x0502 I/O Device can be used as a telephone. When not in use as a telephone, handset is used as a bi-directional audio device. Down Line Phone 0x0503 I/O A standard telephone set connected to the device. When not in use as a telephone, it can be used as a bidirectional audio device. 2.6 External Terminal Types These Terminal Types describe external resources and connections that do not fit under the categories of Input or Output Terminals because they do not necessarily translate acoustic signals to or from the user of the computer. Most of them may be either Input or Output Terminals. USB Device Class Definition for Terminal Types Release 1.0 March 18, 1998 10 Table 2-6 External Terminal Types Terminal Type Code I/O Description External Undefined 0x0600 I/O External Terminal, undefined Type. Analog connector 0x0601 I/O A generic analog connector. Digital audio interface 0x0602 I/O A generic digital audio interface. Line connector 0x0603 I/O An analog connector at standard line levels. Usually uses 3.5mm. Legacy audio connector 0x0604 I/O An input connector assumed to be connected to the lineout of the legacy audio system of the host computer. Used for backward compatibility. S/PDIF interface 0x0605 I/O An S/PDIF digital audio interface. The Associated Interface descriptor can be used to reference an interface used for controlling special functions of this interface. 1394 DA stream 0x0606 I/O An interface to audio streams on a 1394 bus. 1394 DV stream soundtrack 0x0607 I/O An interface to soundtrack of A/V stream on a 1394 bus. 2.7 Embedded Function Terminal Types These Terminal Types represent connections to internal audio sources or sinks in a device. All have associated interfaces for control. These interfaces may be HID or other classes (vendor-specific, mass storage for CD-ROM, etc.). Devices capable of both playback and recording should follow the rules for bidirectional Terminals. Table 2-7 Embedded Terminal Types Terminal Type Code I/O Description Embedded Undefined 0x0700 I/O Embedded Terminal, undefined Type. Level Calibration Noise Source 0x0701 O Internal Noise source for level calibration (MPEG decoding, Dolby PrologicÔ, AC-3 etc.) Equalization Noise 0x0702 O Internal Noise source for measurements. CD player 0x0703 I Audio compact disc player or CD-ROM capable of audio playback. DAT 0x0704 I/O Digital Audio Tape. DCC 0x0705 I/O Digital Compact Cassette. 1 - 6 - 11 ここを編集
https://w.atwiki.jp/ccapac_apu/pages/32.html
[Rasterize] HintingMode=3 AntiAliasMode=2 NormalWeight=0 BoldWeight=0 ItalicSlant=0 Saturation=8 [Misc] MaxHeight=72 Interpolation=6,5,8 VerticalText=0 ModuleListOrder=0 [FreeType] LcdFilter=2 [Cache] MaxFamilies=8 MaxStyles=12 MaxBytes=8388608 [UnloadDLL] imejpmgr.exe msdev.exe devenv.exe
https://w.atwiki.jp/slashblade/pages/17.html
Blade Soul Ingot How to GetCrafting Common Repair MaterialCost Level -25 Cost 0 can t repair EnchantedBlade Stand LeftClickadd Enchant 75% SpecialEnchants How to GetCrafting Oak FenceSneak Right ClickSpawn Entity/BladeStand/Single
https://w.atwiki.jp/artofagile/pages/15.html
Today - / Yesterday - / Total - VMware Server Console に ubuntu 8.10-desktop インストール ubuntu 8.10-desktop いれてみた 手順 更新日 2009-03-22
https://w.atwiki.jp/saskin/pages/12.html
《SA公式Website》 【SuddenAttack 日本公式Website】http //suddenattack.redbanana.jp/ 【SuddenAttack 韓国公式Website】http //suddenattack.netmarble.net/ 【SuddenAttack 中国公式Website】http //www.tuxi.com.cn/index.html 《Skin配布Website(海外)》 【Zenyr s S.A. Visual Development】http //zenyrskin.innori.com/ 【Ghanats Lucy S.A Skin s】http //ghanats.tistory.com/category 【Sudden Skin Maker General】http //gen.gg.gg/ 【Counter-Strike 1.6 radio】http //www.fpsbanana.com/sounds/download/21 《Skin配布Website(日本)》 【サドンアタック†戦友へ送る最後のスキン†】http //suddenskin.blog19.fc2.com/ 【G U N C E N T E R】http //www.zephyr.dti.ne.jp/~tsutomuu/guncenter/ 【SaWeaponSkin】http //www9.atwiki.jp/saweaponskin/pages/13.html 【サドンアタック スキンblog】http //saskinjolyroger.blog43.fc2.com/ 【サドンアタック スキン工房】http //yuicha007.blog71.fc2.com/ 《スキン編集参考》 【アルファチャンネルについて】http //retouch-weblab.com/photo/qmask/index.html
https://w.atwiki.jp/chapati4it/pages/136.html
Windowsで開発したTomcatのアプリをwarファイルにして、ubunts12.04を入れたVMからdotcloudにデプロイする。 Tomcatでサーブレットを触ってみたら、dotcloudにTomcatで作ったwebアプリをデプロイしてみたくなって、簡単に出来るだろうと思ってたら意外と苦労しました。 目次 アプリケーションの作成 アプリケーションをwarファイルにする VMにwarファイルアップロード dotcloudにアプリケーション仮作成 アプリケーションをdotcloudに送信 アプリの開発はサーブレットを作ってみる参照 warファイルの作成は【Java】EclipseでTomcatプロジェクトのWARファイルを作成 | cozzbox参照 Dotcloudの環境設定はdotCloud - Installing the CLI参照 ディレクトリ作成 まず、ホームディレクトリに「dotcloud/tomcat/first」ってディレクトリを作成します（自分の好きなディレクトリでよいです） コマンド例 mkdir -p ~/dotcloud/tomcat/first cd ~/dotcloud/tomcat/first dotcloudのアプリ作成 「dotcloud create ～」で、dotcloud側にアプリを作成します。 既に作成しているアプリとディレクトリを紐付ける場合は、「dotcloud connect ～」になるのではないかと思います。 コマンド例 dotcloud create first == Creating a sandbox application named "first" == Application "first" created. Connect the current directory to "first"? [Y/n] y == Connecting with the application "first" == Connected with default push options --rsync 途中の選択肢はyでいいと思います。 英語の文章をなんとなくみた感じだと、ここのディレクトリと「first」アプリを紐付けちゃうよ？って意味だと思いました。 dotcloud.yml作成 「~/dotcloud/tomcat/first/dotcloud.yml」を作成します。 コマンド nano dotcloud.yml 内容 www type java 「dotcloud.yml」の内容はこれだけでやりました、 「approot ～」をつけたら上手く出来なかったのですorz warファイルアップロード FFFTPで、VMの「~/dotcloud/tomcat/first/」にJava/Tomcat/サーブレットを作ってみるで作ったアプリのwarファイルをアップロードします。 アップロードしたwarファイルの名前を「ROOT.war」に変更します。「ROOT.war」以外だと上手く行きませんでした…不思議orz ※dotcloudにwarファイルをデプロイすると、通常「http //first-chapati.dotcloud.com/warファイルの名前/」がアプリのルートディレクトリになるのですが、ファイル名を「ROOT.war」にすると、「warファイルの名前」の部分が不要になる便利な裏ワザみたいです。 warファイルのデプロイ 「dotcloud push」で、warファイルをdotcloudのアプリに向かってプッシュします。 アプリを修正したら、またここのディレクトリに置いてプッシュすればいいみたいです。 $ dotcloud push == Pushing code with rsync from "./" to application first building file list ... done ./ ROOT.war dotcloud.yml .dotcloud/ .dotcloud/config 省略 == Application is live at http //first-chapati.dotcloud.com 最後に表示されたURLにアクセスすると、ちゃんとJava/Tomcat/サーブレットを作ってみるで作った画面が表示されました。 Tomcatで作成したwebアプリは、Tomcat以外のサーブレットコンテナ（JBoss、Geronimo、Websphere、Jettyなど）でも基本的に動く物らしいです。 dotcloudには、サーブレットコンテナとして「Jetty」が入っているからwarファイルをデプロイ出来るみたいでした。 Tomcatサンプル Tomcatメモ Tomcat7.0.37のインストールとeclipseの設定(Windows) サーブレットを作ってみる Tomcat7のインストールとwarファイルのデプロイ(ubunts12.04) warファイルをdotcloudにデプロイ サーブレットからJSPに遷移するサンプル サーブレットからCSVファイルをダウンロードするサンプル サーブレットからCSVファイルをダウンロードするサンプル（日本語ファイル名） サーブレットからファイルをダウンロードするサンプル（日本語ファイル名） Basic認証(UserDatabaseRealm)+DIGEST認証 JFreeChartで動的にグラフを出力するサンプル ファイルをアップロードするサンプル(Commons FileUplaod) クロスサイトスクリプティング脆弱性を体験してみるサンプル コメント 名前