Good point! Moron! What on fucking earth did you think I meant? Yeah yeah, implement tree-view menus is a fucking awful way. That's what I meant. Goddamn fucking moron.
I use Javascript to give live feedback on form input using regular expressions. DHTML tree-view menus can be useful for expressing a lot of information.
i dont bother with posting links on here just to get visitors because i know the server can't handle the slashdotting anyway.
You lie. In one sentence you managed to fit two links to your site along with the one in your comment header. You lie. Spaming your site here isn't appreciated or acceptable. Grow up.
So, what you're a spammer/googlebomber who blows his mother. In that case, I hope googlism picks this up that jazperbg is a spamming googlebomber. kiwisparks is a spamming googlebomber. And more to the point, kiwisparks.co.nz is a spamming googlebomber.
Trademarks should only come into issue between competing products which are the exact same type of product (i.e., two different web browsers
Duh, they already do. Your trademark only applies over your industry as defined by common knowledge. There is an exception for very popular names, in which trademark applies over all, but this is not the case here.
Here we have a computer software and hardware company named Phoenix vs another bit of software named Phoenix.
"Wahh! I should be able to release my McDonalds Panini because when you think about it it's not actually burger!"
"This is type 6 washer screw -- don't they understand this computely different to a type 4 washer screw??"
And so on, with distinctions that only people in the industry know, and therefore not being the kind of distinctions that trademark law bothers with.
In New Zealand the first semi-major national chain company has come out with a Linux box. Go to dse.co.nz and search for Mandrake. Until now it was only "mom and pop" (as American's would say) stores, and then you go an empty machine.
One big (big) advantage of WxWindows is that it uses native toolkits which although not mattering to many visual users helps greatly if you ever want disabled or government use of your software.
HTTP as it turns out is a good general purpose protocol. It has download resuming, and compression (zip), and many other features that weaker protocols like FTP don't have. It's also being extended via WebDAV (webdav is mostly a subset but there are planned extensions). Regardless of whether it's a "text transfer" protocol, everyone uses it for images, pdfs and zips, and it's quite good at it.
SOAP isn't anything to do with HTTP. SOAP can go via SMTP for all it cares. People tend to use HTTP, but then they do that for many things anyway.
Also understand that - like the web - all SOAP applications don't need to store state. A stateful protocol would be overkill, when you can implement state in SOAP. HTTP works, and is very well understood by many people.
Finally, SOAP has a specific HTTP header that firewalls can recognise (and then block if need be). Considering that SOAP can be just a wrapper for a request that returns some xml it's often similar to submitting a query to google. It could be dangerous, but so is allowing all kinds of downloads, so you have to get into HTTP filtering anyway.
Secondly, although an individual system can choose not to use Palladium, how difficult is it to do so? What's the social weight against using something else? Can anyone tell me what I'm going to face if I choose to continue using Linux?
Anyone remember the WiReD Jini issue? That issue is my secret joy; a perfect lie with quotes and marketing and The Future as a dot com dream. Funny shit.
No, like Dude! If you don't get enough data down the cable it will just not use half the disk. I just have my data on "rotation" so such a scenario will never happen!
I use Javascript to give live feedback on form input using regular expressions. DHTML tree-view menus can be useful for expressing a lot of information.
So, what you're a spammer/googlebomber who blows his mother. In that case, I hope googlism picks this up that jazperbg is a spamming googlebomber. kiwisparks is a spamming googlebomber. And more to the point, kiwisparks.co.nz is a spamming googlebomber.
See ddrfreak.com
Look you idiot, read the post
Best. Comment. Evar.
You've demonstrated that you're not one to speak for the general public. You're completely out of touch.
Trademark law _in this case_ is quite sane.
Only a geek would remember or care for the differentiation that you're making, which is why it doesn't count.
Here we have a computer software and hardware company named Phoenix vs another bit of software named Phoenix.
"Wahh! I should be able to release my McDonalds Panini because when you think about it it's not actually burger!"
"This is type 6 washer screw -- don't they understand this computely different to a type 4 washer screw??"
And so on, with distinctions that only people in the industry know, and therefore not being the kind of distinctions that trademark law bothers with.
Unfortunately, however, this is what a geoduck looks like.
In New Zealand the first semi-major national chain company has come out with a Linux box. Go to dse.co.nz and search for Mandrake. Until now it was only "mom and pop" (as American's would say) stores, and then you go an empty machine.
Which is pretty mean when you think about it.
One big (big) advantage of WxWindows is that it uses native toolkits which although not mattering to many visual users helps greatly if you ever want disabled or government use of your software.
Did you also have to write your own gui toolkit that way?
They might own other companies. They might even be warning on behalf of others for a cut in the profit. There are all kinds of other scenarios.
HTTP as it turns out is a good general purpose protocol. It has download resuming, and compression (zip), and many other features that weaker protocols like FTP don't have. It's also being extended via WebDAV (webdav is mostly a subset but there are planned extensions). Regardless of whether it's a "text transfer" protocol, everyone uses it for images, pdfs and zips, and it's quite good at it.
SOAP isn't anything to do with HTTP. SOAP can go via SMTP for all it cares. People tend to use HTTP, but then they do that for many things anyway.
Also understand that - like the web - all SOAP applications don't need to store state. A stateful protocol would be overkill, when you can implement state in SOAP. HTTP works, and is very well understood by many people.
Finally, SOAP has a specific HTTP header that firewalls can recognise (and then block if need be). Considering that SOAP can be just a wrapper for a request that returns some xml it's often similar to submitting a query to google. It could be dangerous, but so is allowing all kinds of downloads, so you have to get into HTTP filtering anyway.
You lie.
Yadda yadda... yeah, lets pull a Mozilla on X - that'll turn out well. *rolls-eyes*
Firstly, I like you post.
Secondly, although an individual system can choose not to use Palladium, how difficult is it to do so? What's the social weight against using something else? Can anyone tell me what I'm going to face if I choose to continue using Linux?
Also works well in Opera for Linux (both Flash 5 and the Flash 6 beta)
heh heh heh.
That's it! Read and enjoy people. Thanks dimator!
Anyone remember the WiReD Jini issue? That issue is my secret joy; a perfect lie with quotes and marketing and The Future as a dot com dream. Funny shit.
No, like Dude! If you don't get enough data down the cable it will just not use half the disk. I just have my data on "rotation" so such a scenario will never happen!