ARCS
經 Littlearth - 產品類型: Application / 100% Managed Code / Web Service
請注意: 本頁將在9月 2008 作廢 。
您可從以下連結找到當前的資訊
暢銷產品
在 Web服務
- InfoScope 經 .NETXPERT
- Altova XMLSpy 2012 Enterprise Edition - Installed Users 經 Altova
- Altova XMLSpy 2012 Professional Edition - Installed Users 經 Altova
- Altova MissionKit 2012 for Enterprise Software Architects - Installed Users 經 Altova
- Altova MissionKit 2012 for Professional Software Architects - Installed Users 經 Altova
若您需要為此具體版本購買一份License, 請聯繫我們 以瞭解產品是否有售，以及價格。
本頁所顯示的其他資訊及僅僅用作歷史資料參考，很可能有了較大的變動。
A Web Service designed specifically for locking shared resources, such as a user-license, a suite of data, an installation process. ARCS, which stands for Application Resource Control Service, is installed as an NT Service and interfaces with your application as a Web Service. ARCS has no dependencies on other software infrastructures, e.g. client-networking software, a DBMS, IIS, or any runtime prerequisites. Where your application resides, no installation for ARCS is required; your application just has to be able to communicate via HTTP. ARCS meets the standard of "full recovery", which basically means that it maintains its state through anything short of pulling the power plug.
What's New in ARCS V2.01.03?
- New methods have been added to the Web Service that are very useful for quickly storing and retrieving arbitrary data, e.g. storing session state data across a server farm.
ARCS runs on a single Windows machine as an "NT Service". Your application can make simple requests to ARCS via HTTP. ARCS is a type of software that is commonly known as a "web service" (though using the SOAP protocol is optional). ARCS can be communicated with over an intranet or the internet.
Network file byte-locking is not utilized. DBMS table/record locking is not utilized. Both of those methodologies have known limitations. ARCS is a standalone service that is ideally suited for resource control and does not utilize or depend on any of the myriad of historical methodologies.
ARCS can be installed on any Microsoft Windows OS version that Microsoft supports.
- No runtime prerequisites are necessary, e.g. Java Runtime, .NET Framework.
- No networking software is necessary, e.g. Microsoft
Networks Client, Novell Client. - No DBMS is necessary, e.g. SQL Server.
- No webserver-like software is necessary, e.g. IIS.
- There are no minimum requirements for processor speed, RAM, etc.
There is no installation required on the client machines (where your application is installed). A client machine can run any type of operating system and it may be an end-user workstation or a server of any kind. The client machine may indeed be a server hosting multiple users itself, e.g. a web server. The client machine simply has to be equipped to make HTTP requests. On Windows machines, this is easily accomplished using a "built-in" COM object such as "MSXML2.ServerXMLHTTP".
