With the latest version of Google Chrome, I'm now able to scroll UP using the HP Pavilion touchpad. (A feature not-so-conveniently left out of the initial release.)
Maybe I'm just subconsciously looking for it, but it seems to me that Google Chrome is faster - initial application opening and webpage loading - than Internet Explorer. I still have yet to try Firefox, but will take my chances with Google Chrome for the foreseeable future.
Thursday, October 30, 2008
Wednesday, October 15, 2008
Organic advertising by disclosing your data via APIs
I continue to be impressed by the most recent technology trend of creating application programming interfaces (APIs) for the purpose of exposing commercial data. One such example is Netflix API.
Just think of the countless ways others can create their own applications using the Netflix API: add a movie search capability to your website (without storing any of the information), create a Netflix iPhone app to instantly add a movie to your queue, or post your Netflix movie review scores to a social network site, etc.
Not only does this type of openness allow for new application possibilities, but it also creates an organic way of advertising for those companies willing to share their data. No ad agency costs, no magazine inserts, or TV spots. Just announce that you're opening your data to the Internet, and watch the possibilities unfold.
I only hope other companies, including even those whose core competency may not be technology, think about disclosing their non-personal, non-proprietary information.
Just think of the countless ways others can create their own applications using the Netflix API: add a movie search capability to your website (without storing any of the information), create a Netflix iPhone app to instantly add a movie to your queue, or post your Netflix movie review scores to a social network site, etc.
Not only does this type of openness allow for new application possibilities, but it also creates an organic way of advertising for those companies willing to share their data. No ad agency costs, no magazine inserts, or TV spots. Just announce that you're opening your data to the Internet, and watch the possibilities unfold.
I only hope other companies, including even those whose core competency may not be technology, think about disclosing their non-personal, non-proprietary information.
Monday, October 13, 2008
REST: Representational State Transfer
Another tech entry for my future reference (and those that are IT inclined):
The World Wide Web contains a great example of the software architecture style known as REST. Using the WWW, messages can be communicated via the HyperText Transfer Protocol (HTTP). http://dramse01.blogspot.com/ is known as a Universal Resource Identifier (URI). With the REST architecture, it is important that each entity receive its own unique URI. For example, each blog entry would be considered an entity, and therefore, should be given a unique URI.
As with any software, the ability to create, select, update, and delete information is an invaluable (and typically required) function. This holds true regardless of how the information is stored: in memory, files, databases, etc. The REST architecture equivalent of these most widely needed functions are in the form of the following HTTP methods: POST, GET, PUT, DELETE.
The biggest difference I see in a RESTful application is the abundant use of URIs - which points to not only the location of the application, but to also the specific entity in question. Then with a RESTful application, you rely on four key HTTP methods and supporting criteria. Whereas in other web applications (e.g., Remote Procedure Call (RPC) based apps), there is an emphasis on building out all of the possible actions, passing in the location and which entity requires interaction as part of the command input.
While I'm not sure I entirely understand all the pros and cons of REST yet (as probably indicated in my brief write-up), I'm reviewing GData - Google's Data API - and the REST architecture seems more intuitive as I continue to read.
The World Wide Web contains a great example of the software architecture style known as REST. Using the WWW, messages can be communicated via the HyperText Transfer Protocol (HTTP). http://dramse01.blogspot.com/ is known as a Universal Resource Identifier (URI). With the REST architecture, it is important that each entity receive its own unique URI. For example, each blog entry would be considered an entity, and therefore, should be given a unique URI.
As with any software, the ability to create, select, update, and delete information is an invaluable (and typically required) function. This holds true regardless of how the information is stored: in memory, files, databases, etc. The REST architecture equivalent of these most widely needed functions are in the form of the following HTTP methods: POST, GET, PUT, DELETE.
The biggest difference I see in a RESTful application is the abundant use of URIs - which points to not only the location of the application, but to also the specific entity in question. Then with a RESTful application, you rely on four key HTTP methods and supporting criteria. Whereas in other web applications (e.g., Remote Procedure Call (RPC) based apps), there is an emphasis on building out all of the possible actions, passing in the location and which entity requires interaction as part of the command input.
While I'm not sure I entirely understand all the pros and cons of REST yet (as probably indicated in my brief write-up), I'm reviewing GData - Google's Data API - and the REST architecture seems more intuitive as I continue to read.
Saturday, October 11, 2008
Microsoft's mesh.com
Need a way to remote desktop from work into your windows machine at home? How about gaining access to a document that's on your home computer, while you're at work? Try Microsoft's mesh.com.
While I haven't used remote desktop for any practical purpose - other than to prove it works, I have been using the file-sharing capabilities of mesh.com rather extensively for the past month. Overall, I like it.
Simply put, log onto mesh.com (with your windows live id) and connect your device (limited to windows computers at the moment - mobile and mac "soon") by installing the appropriate software. Then upload any files you'd like (currently a 5GB limit) into the mesh - from either the online web browser interface or placing files into the newly created mesh folders on your local computer. Anytime a file is uploaded or modified within your mesh, a copy is stored on mesh.com, and also propagated out to each of the computers actively signed onto the mesh. If you're not signed on, the next time you log in, or add another device, you'll receive the latest revision of the files.
Mesh.com is certainly not a replacement for Google Apps (more on that subject in a future posting). However, it is a pretty useful in-the-cloud file sharing utility. There's certainly more overhead in the fact that mesh stores copies of your files in multiple places, and requires constant checking/updating to make sure everything is in sync. However, I enjoy it for the online storage and update capabilities.
While I haven't used remote desktop for any practical purpose - other than to prove it works, I have been using the file-sharing capabilities of mesh.com rather extensively for the past month. Overall, I like it.
Simply put, log onto mesh.com (with your windows live id) and connect your device (limited to windows computers at the moment - mobile and mac "soon") by installing the appropriate software. Then upload any files you'd like (currently a 5GB limit) into the mesh - from either the online web browser interface or placing files into the newly created mesh folders on your local computer. Anytime a file is uploaded or modified within your mesh, a copy is stored on mesh.com, and also propagated out to each of the computers actively signed onto the mesh. If you're not signed on, the next time you log in, or add another device, you'll receive the latest revision of the files.
Mesh.com is certainly not a replacement for Google Apps (more on that subject in a future posting). However, it is a pretty useful in-the-cloud file sharing utility. There's certainly more overhead in the fact that mesh stores copies of your files in multiple places, and requires constant checking/updating to make sure everything is in sync. However, I enjoy it for the online storage and update capabilities.
Wednesday, October 8, 2008
Good tech advice: get your DBA certification
Having become a recent fan of TechRepublic.com, I saw a blog posting offering a small piece of advice: Afraid you won't stay IT relevant? Get your DBA certification.
Check out the supporting facts within the posting. Meanwhile, I'm going to study up on getting my Oracle OCA.
Check out the supporting facts within the posting. Meanwhile, I'm going to study up on getting my Oracle OCA.
Subscribe to:
Posts (Atom)