All Downloads are FREE. Search and download functionalities are using the official Maven repository.

de.novanic.eventservice.client.event.domain.Domain Maven / Gradle / Ivy

/*
 * GWTEventService
 * Copyright (c) 2011 and beyond, strawbill UG (haftungsbeschr?nkt)
 *
 * This is free software; you can redistribute it and/or modify it
 * under the terms of the GNU Lesser General Public License as
 * published by the Free Software Foundation; either version 3 of
 * the License, or (at your option) any later version.
 * Other licensing for GWTEventService may also be possible on request.
 * Please view the license.txt of the project for more information.
 *
 * This software is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
 * Lesser General Public License for more details.
 *
 * You should have received a copy of the GNU Lesser General Public
 * License along with this software; if not, write to the Free
 * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
 * 02110-1301 USA, or see the FSF site: http://www.fsf.org.
 */
package de.novanic.eventservice.client.event.domain;

import java.io.Serializable;

/**
 * Domains/contexts are used to specify the range where events should occur and listened. That supports the reuse of
 * events ({@link de.novanic.eventservice.client.event.Event} and listeners ({@link de.novanic.eventservice.client.event.listener.RemoteEventListener}.
 * 
*
Example: *
Your application is a multiplayer online game with a conversation system. You defined the following events and * listeners. *
*
Events: NewUserEvent *
Listeners: ConversationListener, ConversationChannelListener, PlayerListListener *
*
It makes sense to divide your elements into different domains, to ensure that a NewUserEvent affects only the right * context/domain. For example one conversation domain and one game domain. ConversationListener and * ConversationChannelListener should be added to the conversation domain and the PlayerListListener should be added to * the game domain. Now you can distinguish the context of the NewUserEvent. If a user joined a conversation (NewUserEvent * added to conversation domain), the two conversation listeners will recognize it and the PlayerListListener won't be * informed about the NewUserEvent in the conversation context/domain. * * @author sstrohschein *
Date: 15.08.2008 *
Time: 22:42:10 */ public interface Domain extends Serializable, Comparable { /** * Return the name of the domain. * @return domain name */ String getName(); }




© 2015 - 2025 Weber Informatics LLC | Privacy Policy