Original author(s) | Sun Microsystems |
---|---|
Initial release | August 30, 2007 |
Stable release | 0.9.11 / October 29, 2009 |
Written in | Java |
Platform | Java |
Type | MMOG middleware |
License | GPLv2, BSD |
Website | "Project Darkstar" at the Wayback Machine (archived 2010-02-08) |
Project Darkstar is a discontinued open source framework for MMOG development, written in Java and deployed as game engine middleware. Project Darkstar began as a personal project of Jeff Kesselman in 1999, later becoming a research project at Sun Microsystems, [1] aimed to "help developers and operators avoid a range of serious, yet typical, problems associated with massive scale online games, virtual worlds, and social networking applications today, including zone overloading, data corruption, and server underutilization." [2] [3]
Project Darkstar began as a personal project of Jeff Kesselman in 1999 while he was the Senior Game Integration Engineer at the Total Entertainment Network. In 2004, Sun's Game Technology Group was formed by Sun Microsystems' Chief Gaming Officer, Chris Melissinos, [4] and is at that time that Mr. Kesselman brought the third iteration of the project into the group where it was dubbed the "Sun Game Server" (SGS). (The initialism survived in the package names of the Project Darkstar Server until its demise.)
Mr. Kesselman worked on the third version for a year as a solo project in Sun, debuting an early version at the Game Developers' Conference (GDC) that year. Following a reorganization of the Software CTO's office in 2005, Mr. Melissinos and Mr. Kesselman moved the project to Sun Labs under Sun Labs Director Karl Haberl. Karl increased the manpower, adding Seth Proctor and Dan Ellard as co-researchers, as well as contractors James Megquier and Sten Anderson. This team delivered what is now known as the Early Access version, the first working server, for GDC 2005.
On February 2, 2010, in the wake of the purchase of Sun by Oracle, Jim Waldo posted on the "Project Announcement" forum that "Sun Labs engineering effort is no longer being applied to Darkstar development". A number of members of the Sun Labs team and a number of members of the Darkstar community worked for a time on the RedDwarf Server as a successor to Darkstar. [5]
When a Project Darkstar server implementation is run, it either starts a new network or joins one that is currently running. All networks contain clients, server implementations, a Project Darkstar stack on which the server implementations run, and several meta-service nodes that handle traffic between each node in the server stack. A server implementation is a user created program written with the Project Darkstar API. The clients include all client-side applications and games that are connected to a game server in the network.
Project Darkstar was designed to support all features vital to a massively multiplayer game, and at the same time be scalable enough to support non-massive multiplayer online games. [6] As such, there are many features that it supported, with many features implemented and integrated into it actively.[ clarification needed ]
The API of Project Darkstar was the key component for developers who used the technology. With it, they could develop game servers to communicate correctly with their client technology and have a server up and running that runs on top of the Project Darkstar game stack. The API is written to hide the concurrency of the underlying system the stack performs for the developer, so that the program can be written with the illusion that it is single threaded, even though the stack is fully parallel. The main parts of the API include task management, data persistence, and channel communication. [7]
Control of information in a Project Darkstar server is generally handled by tasks, although in some special cases they are not necessary. They are used in instances where storage or retrieval of data must be protected from a server crash or shutdown, as tasks are saved and remembered when they are run, and can be respawned when the server is restarted in the same state as they were in before the crash. [8] This is useful, for instance, when updating character information. If something goes wrong with the server internally, the character information is persisted and on a server restart the character information will be restored from the last state it was in before the crash.[ citation needed ]
The Berkeley DB used by Project Darkstar stores all data that is to be persisted. Anything that is to be stored in the database must also be serializable, as the database is programmed to store binary information. A managed object can be anything from player data (i.e. position, equipment) to internal server data and control logic (i.e. scalable data structure, tasks). The usefulness of managed objects is seen in the instance of a server failure. Since managed objects are updated transactionally, any corrupted data is discarded on the server restart and the managed object is rolled back to its last working state.[ citation needed ]
Channels give developers an easy way of communicating with many clients. The way channels work is by giving clients a way of subscribing to channels such that they can send messages to the channel and receive messages from the channel. When a message is sent to the channel from a client or the server, the message is multicast to all clients who are subscribed to it. It is an abstraction built on top of the communications layer to assist in the development of easy and extensible communication between many clients and the server.[ citation needed ]
Some authors have suggested that the management of Central Object Store and Distributed Random Access might not be realistically possible in a highly interactive game environment. [11]
RedDwarf Server was an open-source middleware solution for developing the server side of massively multiplayer online games. It was the official community fork of Project Darkstar. Once Oracle discontinued support for the project, the community rebranded the latest codebase of Project Darkstar's repositories and released it as RedDwarf Server. [12] RedDwarf inherited the Project Darkstar licensing scheme, with the RedDwarf Server distributed under GPLv2 and the server APIs being made available under the GNU General Public License (GPL) with the classpath exception. The Java and C client APIs—available as part of the RedDwarf project—were distributed under a BSD license. [13]
Clients can communicate with the server using a Java or C API. The community also released client APIs for additional platforms including C#, Python, Objective-C, and ActionScript. [14] RedDwarf Server uses a built-in protocol for network communications. [15]
Java is a high-level, class-based, object-oriented programming language that is designed to have as few implementation dependencies as possible. It is a general-purpose programming language intended to let programmers write once, run anywhere (WORA), meaning that compiled Java code can run on all platforms that support Java without the need to recompile. Java applications are typically compiled to bytecode that can run on any Java virtual machine (JVM) regardless of the underlying computer architecture. The syntax of Java is similar to C and C++, but has fewer low-level facilities than either of them. The Java runtime provides dynamic capabilities that are typically not available in traditional compiled languages.
In distributed computing, a remote procedure call (RPC) is when a computer program causes a procedure (subroutine) to execute in a different address space, which is written as if it were a normal (local) procedure call, without the programmer explicitly writing the details for the remote interaction. That is, the programmer writes essentially the same code whether the subroutine is local to the executing program, or remote. This is a form of client–server interaction, typically implemented via a request–response message passing system. In the object-oriented programming paradigm, RPCs are represented by remote method invocation (RMI). The RPC model implies a level of location transparency, namely that calling procedures are largely the same whether they are local or remote, but usually, they are not identical, so local calls can be distinguished from remote calls. Remote calls are usually orders of magnitude slower and less reliable than local calls, so distinguishing them is important.
The Java Remote Method Invocation is a Java API that performs remote method invocation, the object-oriented equivalent of remote procedure calls (RPC), with support for direct transfer of serialized Java classes and distributed garbage-collection.
Apache Subversion is a version control system distributed as open source under the Apache License. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS).
WebObjects is a discontinued Java web application server and a server-based web application framework originally developed by NeXT Software, Inc.
In computing, a directory service or name service maps the names of network resources to their respective network addresses. It is a shared information infrastructure for locating, managing, administering and organizing everyday items and network resources, which can include volumes, folders, files, printers, users, groups, devices, telephone numbers and other objects. A directory service is a critical component of a network operating system. A directory server or name server is a server which provides such a service. Each resource on the network is considered an object by the directory server. Information about a particular resource is stored as a collection of attributes associated with that resource or object.
Message-oriented middleware (MOM) is software or hardware infrastructure supporting sending and receiving messages between distributed systems. Message-oriented middleware is in contrast to streaming-oriented middleware where data is communicated as a sequence of bytes with no explicit message boundaries. Note that streaming protocols are almost always built above protocols using discrete messages such as frames Ethernet), datagrams UDP, packets IP, cells ATM, et al.
Web development is the work involved in developing a website for the Internet or an intranet. Web development can range from developing a simple single static page of plain text to complex web applications, electronic businesses, and social network services. A more comprehensive list of tasks to which Web development commonly refers, may include Web engineering, Web design, Web content development, client liaison, client-side/server-side scripting, Web server and network security configuration, and e-commerce development.
Push technology, also known as server Push, refers to a communication method, where the communication is initiated by a server rather than a client. This approach is different from the "pull" method where the communication is initiated by a client.
In computing, a solution stack or software stack is a set of software subsystems or components needed to create a complete platform such that no additional software is needed to support applications. Applications are said to "run on" or "run on top of" the resulting platform.
Echo is a web application framework created by the company NextApp. The latest iteration, Echo3, allows writing applications in either server-side Java or client-side JavaScript. Server-side applications do not require developer knowledge of HTML, HTTP, or JavaScript. Client-side JavaScript-based applications do not require a server, but can communicate with one via AJAX.
OPC Unified Architecture is a cross-platform, open-source, IEC62541 standard for data exchange from sensors to cloud applications developed by the OPC Foundation. Distinguishing characteristics are:
Thrift is an IDL and binary communication protocol used for defining and creating services for programming languages. It was developed by Facebook. Since 2020, it is an open source project in the Apache Software Foundation.
DimensioneX is an open source and free Multiplayer Engine.
The Rackspace Cloud is a set of cloud computing products and services billed on a utility computing basis from the US-based company Rackspace. Offerings include Cloud Storage, virtual private server, load balancers, databases, backup, and monitoring.
db4o was an embeddable open-source object database for Java and .NET developers. It was developed, commercially licensed and supported by Actian. In October 2014, Actian declined to continue to actively pursue and promote the commercial db4o product offering for new customers.
Redis is a source-available, in-memory storage, used as a distributed, in-memory key–value database, cache and message broker, with optional durability. Because it holds all data in memory and because of its design, Redis offers low-latency reads and writes, making it particularly suitable for use cases that require a cache. Redis is the most popular NoSQL database, and one of the most popular databases overall. Redis is used in companies like Twitter, Airbnb, Tinder, Yahoo, Adobe, Hulu, Amazon and OpenAI.
OpenStack is a free, open standard cloud computing platform. It is mostly deployed as infrastructure-as-a-service (IaaS) in both public and private clouds where virtual servers and other resources are made available to users. The software platform consists of interrelated components that control diverse, multi-vendor hardware pools of processing, storage, and networking resources throughout a data center. Users manage it either through a web-based dashboard, through command-line tools, or through RESTful web services.
Unity Version Control is a cross-platform commercial distributed version control tool developed by Códice Software for Microsoft Windows, Mac OS X, Linux, and other operating systems. It includes a command-line tool, native GUIs, diff and merge tool and integration with a number of IDEs. It is a full version control stack not based on Git.
{{cite web}}
: |last=
has generic name (help)