Check out this place. I do combat flying with them and they're virtually indestructible. The glider can slam into the ground and you an literally pick it up and go for another fly.
The port hills and parks around Christchurch (NZ) are really good for flying:-).
challenge you to make a C++/C# application that is thread-safe and can scale to millions of pageviews per day without writing a ton of supporting code. With a good J2EE app server, a java coder essentially just has to wrap his thread-unsafe code in a syncronized() statement, and he's done-- his app is now thread-safe.
LOL. Firstly C# has a "lock" statement and C/C++ have libraries with similar functionality.
Secondly, you know nothing about concurrent programming. Simply locking a bit of code doesn't suddenly make your program "thread safe". Get a clue.
That'd be why it would be listed as an unworkable PM device:). Any good physicist knows that the coupled cat/toast engine would eventually stop spinning -- leaving both the cat and the toast suspended in the air sideways.
XSL/XSLT == tells how to display XML data(think FOP), but is itself a valid XML document
That's only a side effect. XSLT lets you transform XML into another text format. That can include HTML for display or other formats such as XML (with a different schema), LaTeX, Postscript etc.
When the spammer knows that theres a real person at the receiving end they INCREASE the amount of spam they send you, and tell all of they're spamming friends
Somewhere an english teacher is crying and doesn't know why.
It *can* be used by web sites to provide an API for programmatic access to that site's data and functionality, but using SOAP in this manner is actually quite redundant: You can do the same thing without SOAP and in a more architecturally sound manner.
Care to explain how you would do it in a more "architecturally sound manner"? Screen scrapping?
Admittedly, WebServices are only one potential application of SOAP.
No, it is being used for RPC (Remote Procedure Call) - a form of IPC (Inter-Process Communications). This is far more dangerous.
Oh balony. Do you think that by calling it RPC or IPC you're making it more dangerous? You can expose as much or as little as you like with SOAP. There's no more 'risk' with SOAP than there is with any other web technology (CGI, ASP, PHP, JSP, etc).
People are exposing programmatic interfaces to mission-critical systems. These interfaces allow other computers to manipulate data on those remote mission-critical systems.
So? And HTTP + Forms allow other computers to manipulate data on those remote mission-critical systems as well. What's your point? That people aren't encrypting SOAP calls or routing through HTTPS?
Do you think that SOAP suddenly exposes every API in your system to the web or something?
Think of having direct access to Amex's customer database vs. having access to their web site. It is a massively different situation.
WTF? You can expose as much or as little as you like with SOAP. If there's a programming flaw that allows you access to Amex's customer database it could just as easily occur in the website. You do realise that websites these days can do just about anything don't you? That includes allowing you to fully access Amex's database (if the website is written to do that).
SOAP definitely has its place. Look at Google or Amazon or any website that has forms. If slashdot had a SOAP interface I could write an application that would regulary to check if any/. posts I made had replies and if there were any it could use an SMS gateway webservice to notify me on my cellphone.
It makes sense for websites to have programatically accesible methods/operations.
If Amex is going to use SOAP to send millions of bank transactions across the live internet (rather than through secure lines or over a tight VPN) then it's their fault -- don't blame SOAP.
Slashdot Mirror
I play it a lot (at home, of course, away from all the cruel teenagers
LOL
Why not go to a rave and dance to good music around people who think it's cool rather than stupid?
Unless all your document templates are stored on the network (as they are in most companies).
Check out this place. I do combat flying with them and they're virtually indestructible. The glider can slam into the ground and you an literally pick it up and go for another fly.
:-).
The port hills and parks around Christchurch (NZ) are really good for flying
(indeed, some argue that ADSL can't be defined as broadband)
My ADSL connection is 8Mb/s (1MB/s). Can that be defined as broadband?
challenge you to make a C++/C# application that is thread-safe and can scale to millions of pageviews per day without writing a ton of supporting code.
With a good J2EE app server, a java coder essentially just has to wrap his thread-unsafe code in a syncronized() statement, and he's done-- his app is now thread-safe.
LOL. Firstly C# has a "lock" statement and C/C++ have libraries with similar functionality.
Secondly, you know nothing about concurrent programming. Simply locking a bit of code doesn't suddenly make your program "thread safe". Get a clue.
It's ok...just wait until he sees me put his pink slip in his
Don't forget to put a cover page on it. You did get the memo didn't you?
You have it backwards.
Writing simple GUIs using drag and drop is easy.
Writing complex GUIs using drag and drop (VB's style of drag and drop) is a pain.
What about core dumps?
I meant three not thread.
Been coding far too much.
Or more accurately:
"Three thousand thread hundred twenty one."
Stoned huh?
Or you could just put the tape in a protective box.
Saves on having to use a high-speed water-jet torch thingymajig.
That'd be why it would be listed as an unworkable PM device :). Any good physicist knows that the coupled cat/toast engine would eventually stop spinning -- leaving both the cat and the toast suspended in the air sideways.
Where's the cat with buttered toast attached to its back?
I have my doubts as to whether he'll actually graduate.
XSL/XSLT == tells how to display XML data(think FOP), but is itself a valid XML document
That's only a side effect. XSLT lets you transform XML into another text format. That can include HTML for display or other formats such as XML (with a different schema), LaTeX, Postscript etc.
Content doesn't matter if you can't communicate that content properly.
C code with no indenting is pretty useless to any human reader.
When the spammer knows that theres a real person at the receiving end they INCREASE the amount of spam they send you, and tell all of they're spamming friends
Somewhere an english teacher is crying and doesn't know why.
Um. Hate to tell you this but that monitor you're sitting infront of has an EMF and so does the planet you're sitting on.
I reckon every successful purchaser (like me) should get together and start a website.
Why? You *surely* knew it was a mistake on their behalf. You weren't "tricked" in anyway.
This will not effect the military P code.
Effects affect things.
guess the main difference is that programmers do not have to send back any changes made to the source code.
Surely that means it's moving away from GPL...
It *can* be used by web sites to provide an API for programmatic access to that site's data and functionality, but using SOAP in this manner is actually quite redundant: You can do the same thing without SOAP and in a more architecturally sound manner.
Care to explain how you would do it in a more "architecturally sound manner"? Screen scrapping?
Admittedly, WebServices are only one potential application of SOAP.
No, it is being used for RPC (Remote Procedure Call) - a form of IPC (Inter-Process Communications). This is far more dangerous.
Oh balony. Do you think that by calling it RPC or IPC you're making it more dangerous? You can expose as much or as little as you like with SOAP. There's no more 'risk' with SOAP than there is with any other web technology (CGI, ASP, PHP, JSP, etc).
People are exposing programmatic interfaces to mission-critical systems. These interfaces allow other computers to manipulate data on those remote mission-critical systems.
So? And HTTP + Forms allow other computers to manipulate data on those remote mission-critical systems as well. What's your point? That people aren't encrypting SOAP calls or routing through HTTPS?
Do you think that SOAP suddenly exposes every API in your system to the web or something?
Think of having direct access to Amex's customer database vs. having access to their web site. It is a massively different situation.
WTF? You can expose as much or as little as you like with SOAP. If there's a programming flaw that allows you access to Amex's customer database it could just as easily occur in the website. You do realise that websites these days can do just about anything don't you? That includes allowing you to fully access Amex's database (if the website is written to do that).
SOAP definitely has its place. Look at Google or Amazon or any website that has forms. If slashdot had a SOAP interface I could write an application that would regulary to check if any
It makes sense for websites to have programatically accesible methods/operations.
If Amex is going to use SOAP to send millions of bank transactions across the live internet (rather than through secure lines or over a tight VPN) then it's their fault -- don't blame SOAP.
What about HTML?
Have you tried Frontpage or Dreamweaver?
Don't you think the layout system of HTML is better than the absolute layout system you're used to?
BTW, IIRC, Netbeans allows you to modify the layout constraints of a component using the component's property box rather than the container's.