-> The way we're working in v6.1 is that the IM alerts will -> each of them be within -> a dll (sometimes 2) and the threading/queueing of it too. -> That way the updates -> should be easy. -> -> BUT if at some point we add a feature to the IM alert -> itself, then it won't be a -> simple dll update anymore.
In my case, we registered v5, and I would need to buy a new license for v6, correct? Which I wouldn't get, until next year's budget. So I will be using v5 for at least the rest of this year. -> -> -> Dirk Bulinckx. -> -----Original Message----- -> From: Servers Alive Discussion List -> [mailto:[EMAIL PROTECTED] On Behalf Of -> Michael Shook -> Sent: Tuesday, February 13, 2007 11:21 PM -> To: Servers Alive Discussion List -> Subject: RE: [SA-list] AIM alerts not being sent? -> -> Just as a thought... -> -> Since the IM part of SA seems to be continually under seige -> as the protocols -> shift, would it make sense for that part of SA to be -> "externalized" to a .dll or -> somesuch so that upgrading that piece of it doesn't mean an -> upgrade to SA in -> it's whole. I envision a separate .dll for each flavor. -> -> The reason I suggest this is that it is policy in my company -> that ANY upgrade be -> extensivly tested before it can be rolled into production, -> and NO beta software -> be used. I suspect this policy is not so unusual. -> Upgrading a .dll would then require quite a bit less testing -> than a whole new -> version of SA and would be easier to implement when changes -> inevitably occur. -> Also, it wouldn't be packaged as beta, so it could be implemented. -> -> -> Michael D. Shook -> Systems Analyst - Data Integration -> Saddle Creek Corporation -> [EMAIL PROTECTED] -> 863 668 4477 (work) -> 863 665 1261 (fax) -> www.saddlecrk.com -> -> -----Original Message----- -> From: Servers Alive Discussion List -> [mailto:[EMAIL PROTECTED] On Behalf Of -> Dirk Bulinckx -> Sent: Tuesday, February 13, 2007 5:06 PM -> To: Servers Alive Discussion List -> Subject: RE: [SA-list] AIM alerts not being sent? -> -> Due to changes in the AIM protocol and changes on the AIM -> server we do know that -> the AIM sending in "older" versions (even in the released -> v6) isn't always -> working. -> In the current beta builds AIM seems to work fine again. -> -> -> Dirk Bulinckx. -> -----Original Message----- -> From: Servers Alive Discussion List -> [mailto:[EMAIL PROTECTED] On Behalf Of -> Leone, Michael -> Sent: Tuesday, February 13, 2007 10:16 PM -> To: Servers Alive Discussion List -> Subject: [SA-list] AIM alerts not being sent? -> -> Here's a weird one ... I set up a new AIm username, for my -> SA to send me AIM -> messages at home. I have verified that the AIM username and -> password works (if I -> run the AIM program on the SA server, I can log in and send -> messages through it -> to others). However, when I run the test in SA, no test -> message is sent. I -> (being the recipient, and logged into my own -> AIM) see the SA username log on, then immediately log off. I -> see no test message -> sent to me at all. And I see nothing in the logs, to -> indicate any problems. And -> when the test fails, I get nothing - no message, no -> indication of log on/log -> off. -> -> -> SA 5.1.1964 Enterprise -> Default messages: "%s - %c - %d" -> -> -> Where to troubleshoot next? -> -> -> -- -> ------------------------------------------------------------ -> Michael Leone, Systems Administrator -> Philadelphia Contributionship -> 210 S. 4th Street, Philadelphia, PA 19106 -> <mailto:[EMAIL PROTECTED]> -> V: 215-627-1752 x1282 -> F: 215-627-5354 -> -> -> To unsubscribe send a message with UNSUBSCRIBE as subject to -> [email protected] -> If you use auto-responders (like out-of-the-office -> messages), then make sure -> that they are not send to the list nor to the individual -> members of the list -> that send a message. Doing this will get you removed from the list. -> -> To unsubscribe send a message with UNSUBSCRIBE as subject to -> [email protected] -> If you use auto-responders (like out-of-the-office -> messages), then make sure -> that they are not send to the list nor to the individual -> members of the list -> that send a message. Doing this will get you removed from the list. -> -> -> -> -------------------------------------- -> The information contained in this message is intended only -> for the use of the -> addressee. If the reader of this message is not the -> intended recipient or agent -> of the intended recipient, you are hereby notified that any -> dissemination, -> distribution, or copying of the message is strictly prohibited. -> -> To unsubscribe send a message with UNSUBSCRIBE as subject to -> [email protected] -> If you use auto-responders (like out-of-the-office -> messages), then make sure -> that they are not send to the list nor to the individual -> members of the list -> that send a message. Doing this will get you removed from the list. -> -> To unsubscribe send a message with UNSUBSCRIBE as subject to -> [email protected] -> If you use auto-responders (like out-of-the-office -> messages), then make sure that they are not send to the list -> nor to the individual members of the list that send a -> message. Doing this will get you removed from the list. -> To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
