From a quick glance, XHTML 2 sounds pretty awesome, namely due to XForms and its proposed implementation of the Model-View-Controller pattern. Also, the form data can be shipped to the server in XML and validated against an XSD which could totally simplify input validation.
The new navigation list tag <nl...> seems pretty useful too. But the non-backwards-compatibility is probably the number one reason for holding this standard back.
HTML 5 seems to address the richness of the GUI a bit more with the audio, video, progress, and nav tags. XHTML 2 sounds great for "enterprise" apps, but doesn't go far enough to provide the multimedia experience some users are demanding.
there are so many good Java frameworks to choose from
This could be viewed as a rhetorical question, but seriously, why ARE there so many Java frameworks? GWT is certainly not the last Java web framework we shall ever see.
To me, the Java language is beautiful, and has a rich API with great third party libraries. Yet doing web stuff is a pain to setup (application server), configure (XML), code (with framework of the day), and maintain (people's real-world implementation using 'frameworks' can be quite terrible -- yes, I'm looking at you, Spring).
...you're fucked. You might have 2+ extra drives, but you'll wait a week for the replacement raid card. With MD, you throw the disks in another box and you're back in business.
It all depends on your application, but if I lose a few seconds of transactions, it is no big deal to me.
If you have the cash to throw at Oracle, then you have the cash to throw at hardware scsi raid or a NAS.
The rest of us will get by quickly and cheaply with software sata raid.
Subdomains won't stop other subdomains from reading the parent domain's cookies. If the parent domain is used to auth (e.g. some sesssionID), a malicious script could retrieve or send data to other subdomains. You'd have to be extra careful about isolating subdomains.
I'm also unsure on the exact specifics of the javascript security model for subdomains.. anyone know?
Replying to an AC isn't the brightest thing to do but....
So, why do you not think replying to an AC is useful?
Granted, the AC does not get the message notification of a reply, but everyone else reading the thread (including the original AC) can read the comment and gain insight, be informed, laugh, etc.
For selling a domain, you should use an escrow service to protect both the buyer and seller. At some point, the domain must go through the transfer process and if the domain is in escrow, no one gets screwed by insufficient funding or a NACK'd transfer request. escrow.com is a generic place but to make it worth your while, $500 or more should be the selling price. Others have listed links to sedo, afternic, etc. that will do the same. Ensure that if the sale does not go through, you may still manage the domain, change nameservers, etc.
For an appraisal, you should go the human route. And get three of them if you think your name is worth $500 or more. Appraisals are VERY arbitrary. Any logs of traffic will be very beneficial to the appraisal process. Lots of hits means lots of cash for pure pay-per-click sites.
Ignore the dollar amounts as they are bogus. But, you can use the information given (search engine query results, various rankings, etc) to make a stronger case for a high asking price.
It might be a good idea to check if other TLDs of the same domain are registered -- that is an easy indicator that the domain is at least somewhat valuable.
apart from background/text color, and maybe font/font size
Yes- that is exactly what I want to do, change the background color, change the foreground color, change the font and font size, and apply borders and padding.
Not allowing styling of form/input elements to protect the user from bad design is silly. There are plenty of bad designs out there that don't style forms.
From elements should NOT be overridden by the OS. Does 'aqua' override flash-based forms? No. Does it override image-based input elements? No. It allows styling of A/Links. If I make my A look like a 'button', I should expect my INPUT to look the same -- borders, colors, everything.
Has PHP been separated into a programming language and a templating language? Embedding code in HTML is so 90's. The MVC pattern is much more manageable, especially for a group of developers.
Agreed, what you have described is a huge flaw in the way people write PHP code. Granted, a disciplined programmer could create a separate model and view in PHP, but they never do. Just like someone can put SQL in a JSP, but at least Java starts you off on the right path.
If one of my teammates ever puts SQL or advanced logic (not related directly to the display of the page) in a JSP, I will kick them square in the junk.
A large solar collector would also shade the ground and absorb the heat (energy) that the surrounding ground and air would normally receive. I guess, taking extra heat (energy) from one place, and adding it to lots of others may not be bad...
What about the cost in sending that energy down the wire? Would it be best to build one big-ass solar array? Or would it be better to distribute smaller collectors over a large area, even if the sunlight is not optimal?
Yeah, the "real" games are great, but with a modded xbox, the Xbox Media Center (XBMC) rocks. Also, checkout Super Mario War: http://smw.72dpiarmy.com/
Good point -- web stats can be amazingly useless. Don't read too much into them (oh gnos! I was crawled by wget!). And take the time to research what the numbers mean.
Webstats can be useful for showing broken links (Why so many 404s for this file? Oh crap, Sally renamed it). They can also point out commonly mising files (robots.txt, favicon.ico, sitemap.xml or whatever). Web stats can also be used for optimization -- seeing 4000 hits with only 30 visits might mean you are using way too many images. (So go back and change the fun-looking menu to text.)
Agreed. It is best to place awstats behind.htaccess or some other non-public mechanism. Also, don't click on referral links in the web logs! The setup for multiple domains is a pain, but necessary with any other stats package I've used.
Instead of focusing on the registrar, one could target registries and appeal for some action. But like the grandparent said, it's all about the Benjamins. VeriSign (.com/.net operator) loves the PPC and domain after market. It means they get their $6 times hundreds of millions.
You might try contacing whoever's running the nameserver that's got your domain on it to point it at your own servers, if they're not the same as the miscreants.
Good idea. Hopefully your domain is not on the registrar's nameservers.
You may end up having to pay the miscreants a transfer fee.
You will not pay the losing registrar anything. You only have to pay the new registrar who is gaining the domain.
They do have to release registrar locks in a reasonable time with some reasonable process.
Correct. Your best course of action is calling your current regisrar's phone support repeatedly until you can escalate your call to management or someone in the engineering or technical department. Even if the domain has been lost in their system, they can use the regisrar's web interface to manually unlock the domain.
What TLD (top level domain) does your domain belong to? If it is a.com or.net domain, you will need to retrieve an 'auth code' before you may transfer it. This change from RRP to EPP (the EPP standard requires auth codes) is happening now or has just happened for your registrar. Other TLDs that require auth codes that use EPP are.org and.info. Most likely, your domain does not have an auth code set, but needs one. Ensure your losing registrar sets an auth code for your domain.
Make sure you get an auth code from your 'miscreant' registrar when they unlock the domain. When you do a WHOIS and see that the status 'EPP clientTransferProhibited' has been removed, initiate the transfer request from another registrar.
You are correct in that VeriSign has moved to EPP from RRP (check the RFC's for more info) which enables auth codes on com/net domains. In the transition, all 'old' domains will not have auth codes, while all 'new' domains will have them.
This has nothing to do with "thin/thick". "thin" means the whois data is provided by each registrar (e.g. GoDaddy). "thick" means whois data is stored at and provided by the registry (e.g Afilias).
In the future, it will be difficult to "steal" a domain by transferring it -- as one would need the auth code. Unfortunately, this has nothing to do with zealous registrars arbitrarily putting domains on "registrar hold" (which removes the nameservers from the tld root dns servers).
The scarier thing is this Net non-neutrality stuff. I think the powers that be finally "get it", they realize that DRM by definition won't work so they want to cripple our access to all of those free supermarket samples so we will begrudingly accept their DRM-infected product. DRM is a fence they are building around themselves. Who cares, really? But Net non-neutrality is a fence they can still build around other stuff. That's a problem.
(Just echoing this point as a way to give it a complement.)
Slashdot Mirror
From a quick glance, XHTML 2 sounds pretty awesome, namely due to XForms and its proposed implementation of the Model-View-Controller pattern. Also, the form data can be shipped to the server in XML and validated against an XSD which could totally simplify input validation.
The new navigation list tag <nl ...> seems pretty useful too. But the non-backwards-compatibility is probably the number one reason for holding this standard back.
HTML 5 seems to address the richness of the GUI a bit more with the audio, video, progress, and nav tags. XHTML 2 sounds great for "enterprise" apps, but doesn't go far enough to provide the multimedia experience some users are demanding.
This could be viewed as a rhetorical question, but seriously, why ARE there so many Java frameworks? GWT is certainly not the last Java web framework we shall ever see.
To me, the Java language is beautiful, and has a rich API with great third party libraries. Yet doing web stuff is a pain to setup (application server), configure (XML), code (with framework of the day), and maintain (people's real-world implementation using 'frameworks' can be quite terrible -- yes, I'm looking at you, Spring).
...you're fucked. You might have 2+ extra drives, but you'll wait a week for the replacement raid card. With MD, you throw the disks in another box and you're back in business.
It all depends on your application, but if I lose a few seconds of transactions, it is no big deal to me.
If you have the cash to throw at Oracle, then you have the cash to throw at hardware scsi raid or a NAS.
The rest of us will get by quickly and cheaply with software sata raid.
Wikipedia seems the best place for the author's "how to download and use offline".
Subdomains won't stop other subdomains from reading the parent domain's cookies. If the parent domain is used to auth (e.g. some sesssionID), a malicious script could retrieve or send data to other subdomains. You'd have to be extra careful about isolating subdomains.
I'm also unsure on the exact specifics of the javascript security model for subdomains.. anyone know?
So, why do you not think replying to an AC is useful?
Granted, the AC does not get the message notification of a reply, but everyone else reading the thread (including the original AC) can read the comment and gain insight, be informed, laugh, etc.
Have you checked out Google's 411 yet?
http://labs.google.com/goog411/
If you read the privacy policy: http://labs.google.com/goog411/privacy.html
It says Google stores your voice commands. I assume they could "voice print" the caller even with caller ID blocked.
I guess they won't be able to now, unless they license the patent.
For an appraisal, you should go the human route. And get three of them if you think your name is worth $500 or more. Appraisals are VERY arbitrary. Any logs of traffic will be very beneficial to the appraisal process. Lots of hits means lots of cash for pure pay-per-click sites.
Some automated appraisers are:
http://leapfish.com/
http://dnscoop.com/
Ignore the dollar amounts as they are bogus. But, you can use the information given (search engine query results, various rankings, etc) to make a stronger case for a high asking price.
It might be a good idea to check if other TLDs of the same domain are registered -- that is an easy indicator that the domain is at least somewhat valuable.
What? Not having to: object.toPrimitiveValue() is great! Use the object where you allow NULLs and use the primitive otherwise.
step 1) Cut a hole in a box
step 2) Put your junk in that box
Yes- that is exactly what I want to do, change the background color, change the foreground color, change the font and font size, and apply borders and padding.
Not allowing styling of form/input elements to protect the user from bad design is silly. There are plenty of bad designs out there that don't style forms.
From elements should NOT be overridden by the OS. Does 'aqua' override flash-based forms? No. Does it override image-based input elements? No. It allows styling of A/Links. If I make my A look like a 'button', I should expect my INPUT to look the same -- borders, colors, everything.
My biggest beef with Safari is that it does not style form elements such as , , , etc.
Agreed, passing one test is silly. We need some suite of tests.
Agreed, what you have described is a huge flaw in the way people write PHP code. Granted, a disciplined programmer could create a separate model and view in PHP, but they never do. Just like someone can put SQL in a JSP, but at least Java starts you off on the right path.
If one of my teammates ever puts SQL or advanced logic (not related directly to the display of the page) in a JSP, I will kick them square in the junk.
So ... accountability in voting will be a joke for the foreseeable future because it costs too much?
And accountability in voting will be a joke because the first implementation was a total fuck up?
In software, the solution to this problem would be: eVoting 2.0
Changelog:
A large solar collector would also shade the ground and absorb the heat (energy) that the surrounding ground and air would normally receive. I guess, taking extra heat (energy) from one place, and adding it to lots of others may not be bad...
What about the cost in sending that energy down the wire? Would it be best to build one big-ass solar array? Or would it be better to distribute smaller collectors over a large area, even if the sunlight is not optimal?
Yeah, the "real" games are great, but with a modded xbox, the Xbox Media Center (XBMC) rocks. Also, checkout Super Mario War: http://smw.72dpiarmy.com/
Good point -- web stats can be amazingly useless. Don't read too much into them (oh gnos! I was crawled by wget!). And take the time to research what the numbers mean.
Webstats can be useful for showing broken links (Why so many 404s for this file? Oh crap, Sally renamed it). They can also point out commonly mising files (robots.txt, favicon.ico, sitemap.xml or whatever). Web stats can also be used for optimization -- seeing 4000 hits with only 30 visits might mean you are using way too many images. (So go back and change the fun-looking menu to text.)
Agreed. It is best to place awstats behind .htaccess or some other non-public mechanism.
Also, don't click on referral links in the web logs!
The setup for multiple domains is a pain, but necessary with any other stats package I've used.
Instead of focusing on the registrar, one could target registries and appeal for some action. But like the grandparent said, it's all about the Benjamins. VeriSign (.com/.net operator) loves the PPC and domain after market. It means they get their $6 times hundreds of millions.
Good idea. Hopefully your domain is not on the registrar's nameservers.
You will not pay the losing registrar anything. You only have to pay the new registrar who is gaining the domain.
Correct. Your best course of action is calling your current regisrar's phone support repeatedly until you can escalate your call to management or someone in the engineering or technical department. Even if the domain has been lost in their system, they can use the regisrar's web interface to manually unlock the domain.
What TLD (top level domain) does your domain belong to? If it is a .com or .net domain, you will need to retrieve an 'auth code' before you may transfer it. This change from RRP to EPP (the EPP standard requires auth codes) is happening now or has just happened for your registrar. Other TLDs that require auth codes that use EPP are .org and .info. Most likely, your domain does not have an auth code set, but needs one. Ensure your losing registrar sets an auth code for your domain.
Make sure you get an auth code from your 'miscreant' registrar when they unlock the domain. When you do a WHOIS and see that the status 'EPP clientTransferProhibited' has been removed, initiate the transfer request from another registrar.
Good Luck.You are correct in that VeriSign has moved to EPP from RRP (check the RFC's for more info) which enables auth codes on com/net domains. In the transition, all 'old' domains will not have auth codes, while all 'new' domains will have them.
This has nothing to do with "thin/thick". "thin" means the whois data is provided by each registrar (e.g. GoDaddy). "thick" means whois data is stored at and provided by the registry (e.g Afilias).
In the future, it will be difficult to "steal" a domain by transferring it -- as one would need the auth code. Unfortunately, this has nothing to do with zealous registrars arbitrarily putting domains on "registrar hold" (which removes the nameservers from the tld root dns servers).
I want two things from IE7:
1) full CSS3 support
2) accept the application/xml+xhtml MIME type (for valid xhtml 1.1 pages)
(Just echoing this point as a way to give it a complement.)
Reminds me of reading=
email from the command=
line.=
Is the storage built-in or does it use some form of removable card?