[Beepcore-java-commits] CVS: beepcore-java/src/org/beepcore/beep/profile/sasl SASLProfile.java,1.4,1.5

[Huston F. <hu...@us...>]

Update of /cvsroot/beepcore-java/beepcore-java/src/org/beepcore/beep/profile/sasl
In directory usw-pr-cvs1:/tmp/cvs-serv8402

Modified Files:
	SASLProfile.java 
Log Message:
Changed to use new sendXXX methods on Message instead of the methods on Channel

Index: SASLProfile.java
===================================================================
RCS file: /cvsroot/beepcore-java/beepcore-java/src/org/beepcore/beep/profile/sasl/SASLProfile.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -r1.4 -r1.5
*** SASLProfile.java	2001/07/03 20:51:28	1.4
--- SASLProfile.java	2001/07/30 13:07:11	1.5
***************
*** 72,126 ****
  
      /**
-      * Method sendReply This is usually used for sending challenges
-      * in response to authentication requests...or in response
-      * to authentication attempts.  It was simpler to do it here once
-      * and wrap the exceptions as SASLExceptions than it was to replicate
-      * this code all over the SASL portion of the library.
-      * 
-      * @param blob the data to send
-      * @param Channel the channel to send the data on
-      * 
-      * @throws SASLException if an issue is encountered during the send.
-      */
-     public void sendReply(Blob blob, Channel channel)
-             throws SASLException
-     {
-         try {
-             channel.sendRPY(new StringDataStream(blob.toString()));
-         } catch (Exception x) {
-             throw new SASLException(x.getMessage());
-         }
-     }
- 
-     /**
-      * This routine is typically used for ...
-      * either at the beginning of the authentication
-      * "I would like to authenticate as <blank>"
-      * "I got your challenge.  Here is the info to authenticate me"
-      */
-     /**
-      * Method sendMessage This is usually used for sending
-      * messages in response to challenges from SASL mechanisms
-      * It was simpler to do it here once
-      * and wrap the exceptions as SASLExceptions than it was to replicate
-      * this code all over the SASL portion of the library.
-      * 
-      * @param blob the data to send
-      * @param Channel the channel to send the data on
-      * 
-      * @throws SASLException if an issue is encountered during the send.
-      */                                
-     public void sendMessage(Blob blob, Channel channel)
-             throws SASLException
-     {
-         try {
-             channel.sendMSG(new StringDataStream(blob.toString()),
-                             (ReplyListener) channel.getDataListener());
-         } catch (Exception x) {
-             throw new SASLException(x.getMessage());
-         }
-     }
- 
-     /**
       * Method clearCredential simply clears the credentials associated
       * with a given Session - this is typically done before a new
--- 72,75 ----