1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
|
/*
* Jitsi, the OpenSource Java VoIP and Instant Messaging client.
*
* Copyright @ 2015 Atlassian Pty Ltd
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package net.java.sip.communicator.impl.protocol.zeroconf;
import java.io.*;
import java.net.*;
import net.java.sip.communicator.service.protocol.*;
import net.java.sip.communicator.util.*;
/**
* Instant messaging functionalities for the Zeroconf protocol.
*
* @author Christian Vincenot
*
*/
public class OperationSetBasicInstantMessagingZeroconfImpl
extends AbstractOperationSetBasicInstantMessaging
{
private static final Logger logger
= Logger.getLogger(OperationSetBasicInstantMessagingZeroconfImpl.class);
/**
* The currently valid persistent presence operation set..
*/
private final OperationSetPersistentPresenceZeroconfImpl opSetPersPresence;
/**
* The protocol provider that created us.
*/
private final ProtocolProviderServiceZeroconfImpl parentProvider;
/**
* Creates an instance of this operation set keeping a reference to the
* parent protocol provider and presence operation set.
*
* @param provider The provider instance that creates us.
* @param opSetPersPresence the currently valid
* <tt>OperationSetPersistentPresenceZeroconfImpl</tt> instance.
*/
public OperationSetBasicInstantMessagingZeroconfImpl(
ProtocolProviderServiceZeroconfImpl provider,
OperationSetPersistentPresenceZeroconfImpl opSetPersPresence)
{
this.opSetPersPresence = opSetPersPresence;
this.parentProvider = provider;
}
@Override
public Message createMessage(String content, String contentType,
String encoding, String subject)
{
return new MessageZeroconfImpl(content, encoding, contentType,
MessageZeroconfImpl.MESSAGE);
}
/**
* Sends the <tt>message</tt> to the destination indicated by the
* <tt>to</tt> contact.
*
* @param to the <tt>Contact</tt> to send <tt>message</tt> to
* @param message the <tt>Message</tt> to send.
* @throws IllegalStateException if the underlying Zeroconf stack is not
* registered and initialized.
* @throws IllegalArgumentException if <tt>to</tt> is not an instance
* belonging to the underlying implementation.
*/
public void sendInstantMessage(Contact to, Message message) throws
IllegalStateException, IllegalArgumentException
{
if( !(to instanceof ContactZeroconfImpl) )
throw new IllegalArgumentException(
"The specified contact is not a Zeroconf contact."
+ to);
MessageZeroconfImpl msg =
(MessageZeroconfImpl)createMessage(message.getContent());
deliverMessage(msg, (ContactZeroconfImpl)to);
}
/**
* In case the to the <tt>to</tt> Contact corresponds to another zeroconf
* protocol provider registered with SIP Communicator, we deliver
* the message to them, in case the <tt>to</tt> Contact represents us, we
* fire a <tt>MessageReceivedEvent</tt>, and if <tt>to</tt> is simply
* a contact in our contact list, then we simply echo the message.
*
* @param message the <tt>Message</tt> the message to deliver.
* @param to the <tt>Contact</tt> that we should deliver the message to.
*/
private void deliverMessage(Message message, ContactZeroconfImpl to)
{
ClientThread thread = to.getClientThread();
try
{
if (thread == null)
{
Socket sock;
if (logger.isDebugEnabled())
logger.debug("ZEROCONF: Creating a chat connexion to "
+to.getIpAddress()+":"+to.getPort());
sock = new Socket(to.getIpAddress(), to.getPort());
thread = new ClientThread(sock, to.getBonjourService());
thread.setStreamOpen();
thread.setContact(to);
to.setClientThread(thread);
thread.sendHello();
if (to.getClientType() == ContactZeroconfImpl.GAIM)
{
try
{
Thread.sleep(300);
}
catch (InterruptedException ex)
{
logger.error(ex);
}
}
}
//System.out.println("ZEROCONF: Message content => "+
//message.getContent());
thread.sendMessage((MessageZeroconfImpl) message);
fireMessageDelivered(message, to);
}
catch (IOException ex)
{
logger.error(ex);
}
}
/**
* Notifies all registered message listeners that a message has been
* received.
*
* @param message the <tt>Message</tt> that has been received.
* @param from the <tt>Contact</tt> that <tt>message</tt> was received from.
*/
@Override
public void fireMessageReceived(Message message, Contact from)
{
super.fireMessageReceived(message, from);
}
/**
* Determines whether the protocol provider (or the protocol itself) support
* sending and receiving offline messages. Most often this method would
* return true for protocols that support offline messages and false for
* those that don't. It is however possible for a protocol to support these
* messages and yet have a particular account that does not (i.e. feature
* not enabled on the protocol server). In cases like this it is possible
* for this method to return true even when offline messaging is not
* supported, and then have the sendMessage method throw an
* OperationFailedException with code - OFFLINE_MESSAGES_NOT_SUPPORTED.
*
* @return <tt>true</tt> if the protocol supports offline messages and
* <tt>false</tt> otherwise.
*/
public boolean isOfflineMessagingSupported()
{
return true;
}
/**
* Determines whether the protocol supports the supplied content type
*
* @param contentType the type we want to check
* @return <tt>true</tt> if the protocol supports it and
* <tt>false</tt> otherwise.
*/
public boolean isContentTypeSupported(String contentType)
{
return contentType.equals(DEFAULT_MIME_TYPE);
}
}
|
