Oh yes... the TI 99/4A. That was my first computer as well. Learned BASIC on that had fun with all the sprite and sound functions in TI's extended BASIC. That was fun for a couple months, then I decided I needed something more fulfilling and got a Commodore 64. Ahh.. the days of LOAD "TELENGARD",8,1
Unless the manufacturer was IOMEGA!! Than they try to find anyway possible to convince you that it was your fault and they will not replace the item in question.
I have to agree with the sentiment here. I first discovered XML when creating a Java Servlet based application. I wanted an easy and flexible way to create messages between the servlets in my application. Of course this was when SOAP was still called XML-RPC. I thought that XML was well suited for describing messages and document structure.
I think rather than replacing VB, XAML could replace the ugly mess of asp: tags in an ASP.NET application.:)
Along those lines would be a book with useful examples of Web Services in the real world. It would be great if this book showed not just.NET, but other non-MS technologies. Along with reasons why they did or did not use.NET ( or Java, or whatever they used ).
I think that people could probably find exploits in Apache, Sendmail, etc... probably a lot easier since they can scan the sourcecode. From what I have read though, most of these worms & virii are not very complicated and are using relatively easy to exploit holes in M$ products. Most of these holes exist since M$ is trying to make life easier on the user by doing work behind the scenes (such as automatically calling an IE dll to render an HTML email). As work continues on desktop environments such as GNOME and KDE, I think that it is not unreasonable to expect to see exploits in those products being used. But since M$ products dominate the desktop market, I expect to find most people writing worms&virii for M$ environments.
I do have to say... I think that accessing primitive types as objects is definately an improvement over Java. If the the memory management in the implementations is better than the memory management in most JVMs, then Sun will really have some catching up to do. Only think I dislike is that we will be back to COMs multiple-inheritance hell.
If you actually look at the page, most of the filetypes that are being excluded probably are best not sent in Email form anyway. It doesn't really hurt the functionality of Outlook. 'course I still think it would have been easier just to throw a dialog box saying that the attachment may have come from an insecure source... same as in Word, Excel, etc... remember all "Office" products are supposed to look the same... right?;)
We run a few machines with Mandrake 6.1 and some of our machines run fine, others seem to crash for no reason. Not sure it can be blamed on the kernel and glibc2.1.2 being compiled with pgcc or not though.
In 6.0 though, we did have problems with some self-compiled kernel's not being able to be loaded by lilo!!
Slashdot Mirror
Oh yes... the TI 99/4A. That was my first computer as well. Learned BASIC on that had fun with all the sprite and sound functions in TI's extended BASIC. That was fun for a couple months, then I decided I needed something more fulfilling and got a Commodore 64. Ahh.. the days of LOAD "TELENGARD",8,1
Unless the manufacturer was IOMEGA!! Than they try to find anyway possible to convince you that it was your fault and they will not replace the item in question.
I have to agree with the sentiment here. I first discovered XML when creating a Java Servlet based application. I wanted an easy and flexible way to create messages between the servlets in my application. Of course this was when SOAP was still called XML-RPC. I thought that XML was well suited for describing messages and document structure.
:)
I think rather than replacing VB, XAML could replace the ugly mess of asp: tags in an ASP.NET application.
Along those lines would be a book with useful examples of Web Services in the real world. It would be great if this book showed not just .NET, but other non-MS technologies. Along with reasons why they did or did not use .NET ( or Java, or whatever they used ).
I think that people could probably find exploits in Apache, Sendmail, etc... probably a lot easier since they can scan the sourcecode. From what I have read though, most of these worms & virii are not very complicated and are using relatively easy to exploit holes in M$ products. Most of these holes exist since M$ is trying to make life easier on the user by doing work behind the scenes (such as automatically calling an IE dll to render an HTML email). As work continues on desktop environments such as GNOME and KDE, I think that it is not unreasonable to expect to see exploits in those products being used. But since M$ products dominate the desktop market, I expect to find most people writing worms&virii for M$ environments.
Now I can't listen to any of the Dodger games at work unless I subscribe to mlb.com (damn kxta1150.com)! Isn't anything free anymore? ;)
I do have to say... I think that accessing primitive types as objects is definately an improvement over Java. If the the memory management in the implementations is better than the memory management in most JVMs, then Sun will really have some catching up to do. Only think I dislike is that we will be back to COMs multiple-inheritance hell.
If you actually look at the page, most of the filetypes that are being excluded probably are best not sent in Email form anyway. It doesn't really hurt the functionality of Outlook. 'course I still think it would have been easier just to throw a dialog box saying that the attachment may have come from an insecure source... same as in Word, Excel, etc... remember all "Office" products are supposed to look the same... right? ;)
We run a few machines with Mandrake 6.1 and some of our machines run fine, others seem to crash for no reason. Not sure it can be blamed on the kernel and glibc2.1.2 being compiled with pgcc or not though.
In 6.0 though, we did have problems with some self-compiled kernel's not being able to be loaded by lilo!!
Look for HCF or HSP on the modem box, manual, driver CD, etc... if its there, its a WinModem.