Can one of admins take a look at the Earthlink subscribtion and unsubscribe them. Sam
-----Original Message----- From: Earthlink Abuse Department [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 2:33 PM To: [EMAIL PROTECTED] Subject: Re: SIP Servlet revisited Hello, You are receiving this message in follow-up to a report received by the EarthLink Abuse Department. You may have submitted this report to a number of addresses including but not limited to [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], or [EMAIL PROTECTED] Most reports of network abuse sent to this department fall into a few recognizable categories (spam, cracking, viruses, etc.). To increase efficiency, our filters scan incoming reports and attempt to determine the general type of issue being reported. We were not able to process your report because it does not appear to include the information needed for EarthLink Abuse to begin it's investigation. Evidence to Abuse should always include the IP address of the offending party and a valid timestamp, which includes time, date and timezone. To learn how to report spam so action is taken: http://spam.abuse.net/userhelp/howtocomplain.shtml To learn how to locate and interpret e-mail headers in your e-mail client: http://support.earthlink.net/support/TUTORIALS/email/mbx_interpret_heade rs.jsp Other useful lookup tools: http://samspade.org/ Once you have included the pertinent information needed, please resubmit your report, and include this autoresponse. Your report will then be reprocessed by our filters. However, you should expect to receive another auto-response after your resubmission is re-examined, but due to the large number of reports we receive, please understand that you may not receive a personal response. Our policies can be found at the following page: http://earthlink.net/about/policies/ Thanks, The EarthLink Abuse Staff >Hey Guys, >A little over a year ago the posibility for making an implementation of >the SIP Servlet specification using Tomcat was shortly talked about >(see >http://www.mail-archive.com/[EMAIL PROTECTED]/msg25333.html ) >I have done some tests and looked into what problems this would present >and I came to one conclusion; The current >design of the org.apache.catalina.Session interface requires that you do >some weird hacking, twisting and adaptation to get support >for sessions in SIP, since Session expects to always wrap a HttpSession, >but SIP Servlets have their own session interface. >I have talked to Anders Kristensen about these difference session >interfaces. He said that even though there had been talks with >the Servlet expert group about making a general servlet session >interface fitting the need of both HTTP and SIP it was voted against >in the Servlet expert group. The reason they gave for not making such an >interface was the small spread and use of SIP servlets. >Until such an interface is designed I was wondering if it would be >possible to change the org.apache.catalina.Session interface to >return a temporary internal Tomcat interface that contains the same >methods that would probably end up in the general Servlet >session interface?? >- Brian >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
