behavior_observer

观察者模式

本章任务

1.观察者模式的定义

 

定义:观察者模式定义了一种一队多的依赖关系,让多个观察者对象同时监听某一个主题对象。这个主题对象在状态上发生变化时,会通知所有观察者对象,使他们能够自动更新自己。


2.网上商店中商品在名称 价格等方面有变化,系统自动通知会员。

 

/*
 * @(#)Observer.java	1.20 05/11/17
 *
 * Copyright 2006 Sun Microsystems, Inc. All rights reserved.
 * SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
 */
package com.aptech.behavior.observer;

/**
 * A class can implement the <code>Observer</code> interface when it
 * wants to be informed of changes in observable objects.
 *
 * @author  Chris Warth
 * @version 1.20, 11/17/05
 * @see     java.util.Observable
 * @since   JDK1.0
 */
public interface Observer {
    /**
     * This method is called whenever the observed object is changed. An
     * application calls an <tt>Observable</tt> object's
     * <code>notifyObservers</code> method to have all the object's
     * observers notified of the change.
     *
     * @param   o     the observable object.
     * @param   arg   an argument passed to the <code>notifyObservers</code>
     *                 method.
     */
    void update(Observable o, Object arg);
}

 

/*
 * @(#)Observable.java 1.39 05/11/17
 * 
 * Copyright 2006 Sun Microsystems, Inc. All rights reserved.
 * SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
 */

package com.aptech.behavior.observer;

import java.util.Vector;

/**
 * This class represents an observable object, or "data"
 * in the model-view paradigm. It can be subclassed to represent an
 * object that the application wants to have observed.
 * <p>
 * An observable object can have one or more observers. An observer may be any
 * object that implements interface <tt>Observer</tt>. After an observable
 * instance changes, an application calling the <code>Observable</code>'s
 * <code>notifyObservers</code> method causes all of its observers to be
 * notified of the change by a call to their <code>update</code> method.
 * <p>
 * The order in which notifications will be delivered is unspecified. The
 * default implementation provided in the Observable class will notify Observers
 * in the order in which they registered interest, but subclasses may change
 * this order, use no guaranteed order, deliver notifications on separate
 * threads, or may guarantee that their subclass follows this order, as they
 * choose.
 * <p>
 * Note that this notification mechanism is has nothing to do with threads and
 * is completely separate from the <tt>wait</tt> and <tt>notify</tt> mechanism
 * of class <tt>Object</tt>.
 * <p>
 * When an observable object is newly created, its set of observers is empty.
 * Two observers are considered the same if and only if the <tt>equals</tt>
 * method returns true for them.
 * 
 * @author Chris Warth
 * @version 1.39, 11/17/05
 * @see java.util.Observable#notifyObservers()
 * @see java.util.Observable#notifyObservers(java.lang.Object)
 * @see java.util.Observer
 * @see java.util.Observer#update(java.util.Observable, java.lang.Object)
 * @since JDK1.0
 */
public class Observable {
	private boolean				changed	= false;
	private final Vector	obs;

	/** Construct an Observable with zero Observers. */

	public Observable() {
		obs = new Vector();
	}

	/**
	 * Adds an observer to the set of observers for this object, provided
	 * that it is not the same as some observer already in the set.
	 * The order in which notifications will be delivered to multiple
	 * observers is not specified. See the class comment.
	 * 
	 * @param o
	 *          an observer to be added.
	 * @throws NullPointerException
	 *           if the parameter o is null.
	 */
	public synchronized void addObserver(Observer o) {
		if (o == null)
			throw new NullPointerException();
		if (!obs.contains(o)) {
			obs.addElement(o);
		}
	}

	/**
	 * Deletes an observer from the set of observers of this object.
	 * Passing <CODE>null</CODE> to this method will have no effect.
	 * 
	 * @param o
	 *          the observer to be deleted.
	 */
	public synchronized void deleteObserver(Observer o) {
		obs.removeElement(o);
	}

	/**
	 * If this object has changed, as indicated by the <code>hasChanged</code>
	 * method, then notify all of its observers
	 * and then call the <code>clearChanged</code> method to
	 * indicate that this object has no longer changed.
	 * <p>
	 * Each observer has its <code>update</code> method called with two arguments:
	 * this observable object and <code>null</code>. In other words, this method
	 * is equivalent to: <blockquote><tt>
	 * notifyObservers(null)</tt></blockquote>
	 * 
	 * @see java.util.Observable#clearChanged()
	 * @see java.util.Observable#hasChanged()
	 * @see java.util.Observer#update(java.util.Observable, java.lang.Object)
	 */
	public void notifyObservers() {
		notifyObservers(null);
	}

	/**
	 * If this object has changed, as indicated by the <code>hasChanged</code>
	 * method, then notify all of its observers
	 * and then call the <code>clearChanged</code> method to indicate
	 * that this object has no longer changed.
	 * <p>
	 * Each observer has its <code>update</code> method called with two arguments:
	 * this observable object and the <code>arg</code> argument.
	 * 
	 * @param arg
	 *          any object.
	 * @see java.util.Observable#clearChanged()
	 * @see java.util.Observable#hasChanged()
	 * @see java.util.Observer#update(java.util.Observable, java.lang.Object)
	 */
	public void notifyObservers(Object arg) {
		/*
		 * a temporary array buffer, used as a snapshot of the state of
		 * current Observers.
		 */
		Object[] arrLocal;

		synchronized (this) {
			/*
			 * We don't want the Observer doing callbacks into
			 * arbitrary code while holding its own Monitor.
			 * The code where we extract each Observable from
			 * the Vector and store the state of the Observer
			 * needs synchronization, but notifying observers
			 * does not (should not). The worst result of any
			 * potential race-condition here is that:
			 * 1) a newly-added Observer will miss a
			 * notification in progress
			 * 2) a recently unregistered Observer will be
			 * wrongly notified when it doesn't care
			 */
			if (!changed)
				return;
			arrLocal = obs.toArray();
			clearChanged();
		}

		for (int i = arrLocal.length - 1; i >= 0; i--)
			((Observer) arrLocal[i]).update(this, arg);
	}

	/**
	 * Clears the observer list so that this object no longer has any observers.
	 */
	public synchronized void deleteObservers() {
		obs.removeAllElements();
	}

	/**
	 * Marks this <tt>Observable</tt> object as having been changed; the
	 * <tt>hasChanged</tt> method will now return <tt>true</tt>.
	 */
	protected synchronized void setChanged() {
		changed = true;
	}

	/**
	 * Indicates that this object has no longer changed, or that it has
	 * already notified all of its observers of its most recent change,
	 * so that the <tt>hasChanged</tt> method will now return <tt>false</tt>.
	 * This method is called automatically by the <code>notifyObservers</code>
	 * methods.
	 * 
	 * @see java.util.Observable#notifyObservers()
	 * @see java.util.Observable#notifyObservers(java.lang.Object)
	 */
	protected synchronized void clearChanged() {
		changed = false;
	}

	/**
	 * Tests if this object has changed.
	 * 
	 * @return <code>true</code> if and only if the <code>setChanged</code> method
	 *         has been called more recently than the <code>clearChanged</code>
	 *         method on this object; <code>false</code> otherwise.
	 * @see java.util.Observable#clearChanged()
	 * @see java.util.Observable#setChanged()
	 */
	public synchronized boolean hasChanged() {
		return changed;
	}

	/**
	 * Returns the number of observers of this <tt>Observable</tt> object.
	 * 
	 * @return the number of observers of this object.
	 */
	public synchronized int countObservers() {
		return obs.size();
	}
}

 

package com.aptech.behavior.observer;

/**
 * 
 * 文件名: Product.java
 * 版权: 方勇
 * 描述:产品类 ,主要执行产品数据库插入 更新
 * Email:fangyong2006@163.com
 * 修改时间: 2010-7-9下午09:31:48
 */
public class Product extends Observable {

	// 产品名
	private String	name;
	// 产品价格
	private float		price;

	public String getName() {
		return name;
	}

	public void setName(String name) {
		this.name = name;
		// 设置变化点
		setChanged();
		notifyObservers(name);
	}

	public float getPrice() {
		return price;
	}
	public void setPrice(float price) {
		this.price = price;
		// 设置变化点
		setChanged();
		notifyObservers(new Float(price));
	}

}

 

package com.aptech.behavior.observer;



/**
 * 
 * 文件名: NameObserver.java
 * 版权: 方勇
 * 描述: 观察者NameObserver主要用来对产品名称(name)进行观察的
 * Email:fangyong2006@163.com
 * 修改时间: 2010-7-9下午09:40:49
 */
public class NameObserver implements Observer {

	private String	name	= null;

	public void update(Observable arg0, Object arg1) {
		if (arg1 instanceof String){
			name=(String)arg1;
			// 产品名称改变值在name中
			System.out.println("NameObserver :name changet to "+name);
		}
	}
}

 

package com.aptech.behavior.observer;



/**
 * 
 * 文件名: NameObserver.java
 * 版权: 方勇
 * 描述: 观察者PriceObserver主要用来对产品价格(price)进行观察的
 * Email:fangyong2006@163.com
 * 修改时间: 2010-7-9下午09:40:49
 */
public class PriceObserver implements Observer {

	private float	price	= 0;

	public void update(Observable arg0, Object arg1) {
		if (arg1 instanceof Float) {
			price = ((Float) arg1).floatValue();
			System.out.println("PriceObserver :price changet to " + price);
		}
	}
}

 

package com.aptech.behavior.observer;

import junit.framework.TestCase;

public class ObserverTest extends TestCase {

	@Override
	protected void setUp() throws Exception {
		super.setUp();
	}

	public void testObserver() {
		NameObserver nameobs = new NameObserver();
		PriceObserver priceobs = new PriceObserver();
		// 加入观察者
		Product product = new Product();

		product.addObserver(nameobs);
		product.addObserver(priceobs);

		product.setName("基围虾");
		product.setPrice(15.82f);
	}
}

   

本章目标

1. 理解观察者模式
 

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
图像识别技术在病虫害检测中的应用是一个快速发展的领域,它结合了计算机视觉和机器学习算法来自动识别和分类植物上的病虫害。以下是这一技术的一些关键步骤和组成部分: 1. **数据收集**:首先需要收集大量的植物图像数据,这些数据包括健康植物的图像以及受不同病虫害影响的植物图像。 2. **图像预处理**:对收集到的图像进行处理,以提高后续分析的准确性。这可能包括调整亮度、对比度、去噪、裁剪、缩放等。 3. **特征提取**:从图像中提取有助于识别病虫害的特征。这些特征可能包括颜色、纹理、形状、边缘等。 4. **模型训练**:使用机器学习算法(如支持向量机、随机森林、卷积神经网络等)来训练模型。训练过程中,算法会学习如何根据提取的特征来识别不同的病虫害。 5. **模型验证和测试**:在独立的测试集上验证模型的性能,以确保其准确性和泛化能力。 6. **部署和应用**:将训练好的模型部署到实际的病虫害检测系统中,可以是移动应用、网页服务或集成到智能农业设备中。 7. **实时监测**:在实际应用中,系统可以实时接收植物图像,并快速给出病虫害的检测结果。 8. **持续学习**:随着时间的推移,系统可以不断学习新的病虫害样本,以提高其识别能力。 9. **用户界面**:为了方便用户使用,通常会有一个用户友好的界面,显示检测结果,并提供进一步的指导或建议。 这项技术的优势在于它可以快速、准确地识别出病虫害,甚至在早期阶段就能发现问题,从而及时采取措施。此外,它还可以减少对化学农药的依赖,支持可持续农业发展。随着技术的不断进步,图像识别在病虫害检测中的应用将越来越广泛。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值