Saturday February 11, 2012 @ 10:02:28 GMT+10 ( Weather: n/a )
|
|
|
|
|
Powered byD's Bloggie
| Weblog Archive browse by category ... |
|
|
|
|
Last edited: Sun 2005-12-18 @ 02:01 , by DaRen 2 time(s)
RSS - 4:11 pm
Computing , Internet , Site Issue , Standards -  DaRen
Lately I'm interested in RSS and I'm considering to prioritize and make it the first thing on my todo list.
RSS
(Really Simple Syndication) A syndication format that was developed by Netscape in 1999 and became very popular for aggregating updates to blogs and the latest news from Web sites. RSS has also stood for "Rich Site Summary" and "RDF Site Summary."
RSS is a family of XML file formats and the information is delivered as an XML file called RSS feed, webfeed, RSS stream, or RSS channel.
Drop me a line if you know any good PHP RSS parser/reader/aggregator. I'm also interested in RSS feed generator in PHP. I wanna learn more about RSS feed and put up a feed on my site.
Some feed parsers that "looks" good among others:
- Magpie RSS - packed with hell lots of features and functions, used by alot of RSS software
- LastRSS - light weight RSS parser
- Lilina News Aggregator - some sort of feeds on feeds, using Magpie library
- Tiny Tiny RSS - not tiny at all, web based RSS reader works like desktop version. Using Magpie library
Feed generator/writer:
... haven't test them though..
Weather updates - 4:34 pm
Computing , Cool Stuff , Internet , Site Issue , Site Updates , Website Intro - DaRen
I've added weather updates on mysite, you can find them in top most of my page, on the bottom most of left navigation menu and also here for detailed info.
The latest weather datas are provided by Weather.com .
If you interested in building your own weather reports (web), check out here http://www.w3.weather.com/services/xmloap.html. It's a free registration and Weather.com only requires your email address. After then you can use the partner ID and license key provided and get access to the latest weather data, via xml feed ;)
Which one ? HTML or XHTML ? - 1:48 am
(X)HTML , Browser , Computing , Internet , Site Issue , Standards - DaRen
Currently the site's content is HTML 4.01 Transitional compliance, it works fine until I realize doing a <link> thing inside the header breaks everything... one example is:
[ Hide ] <link rel="shortcut icon" type="image/vnd.microsoft.icon" href='/favicon.ico' />
It doesn't belongs to HTML 4.01...So, Im thinking of changing to XHTML, kinda headache though because I need to search and replace a lot of html tags like <br> to <br /> <input> to <input /> inside my templates...tons of them...omg...gayness...I should standardize my code in the beginning...
Reserved folder name in Win and Unix - 12:54 pm
Computing , Security , Weird Stuff - DaRen
Below is a list of reserved names that cannot be used for folder or file name, either in windows or unix-like file system:
CON, PRN, AUX, CLOCK$, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9.
For example, if you try to create a new folder named, "CON" (case-insensitive), windows will "undo" the renaming to the original one. So creating a new folder with the name "CON" just renames it to "New Folder". Try it yourself if you don't believe.
Explanation
This actually is a unix-like feature. DOS device drivers are accessible like normal files, i.e. the everything-is-a-file philosophy. CON is the equivalent of /dev/tty, NUL of /dev/null, COM# of /dev/ttyS#, LPT# of /dev/lp# and CLOCK$ corresponds to /dev/rtc (PRN is an alias to LPT1, AUX is COM1). Every character device can be opened this way, block devices (which are assumed to be FAT formatted...) are named A: to Z:, as you will know. Many pseudo character devices (drivers which had to be loaded as drivers but were no character devices, like EMM386, HIMEM.SYS, ..) had forbidden characters like '*' in their device names to be hidden from the user.
The only problem is: DOS 1, which introduced CON, NUL, PRN and AUX had no directories, i.e. no /dev/, so for compatibility with old DOS1-executables (which don't know that they live in a directory) the character devices have to exist in every directory. Don't know why this feature was not limited to FCB (CP/M like) file access, unix like file numbers were introduced together with directories in DOS 2
Trick
You can however rename/create folders with those reserved names by using the mkdir and ren command in DOS-prompt.
Last edited: Mon 2005-10-24 @ 16:35 , by DaRen 1 time(s)
CAPTCHA - 4:24 pm
Computing , Security , Site Issue , Standards - DaRen
This is what I'll implement it later to shoutbox/comment section. Shoutbox section should generate a smaller image to save space ? Haven't decide...let me think about it...
CAPTCHA ( Completely automated public turing test to tell computers and humans apart ), click here for more info.
Y2K bug ? What about Y2038 ? - 11:38 pm
Computing , Event , Security , Standards - DaRen
5 years ago, I witnessed the historical moment where time passed by, marking the start of a new millennium. There are a lot of news about the Y2K bug before that, about how it will causes impact to our every day life. But well thanks to those people who done the preparation, fixing and patching on the electronic devices that we rely on, I stepped into the year 2000 without having a single trouble, just that I need to remember not to write year 1999 instead of 2000 when filling up forms.
So, now what? I'm working on some sort of birthday reminder thing in PHP and I got frustrated when it comes to storing a person's birth date. First of all I don't like to use MySQL datetime date type, I prefer using unix epoch which can be easily generated using php time() and mktime(), saving me the steps to converting the format. However unix epoch is only valid from January 1 1970 00:00:00 GMT onwards, making those people who born before 1970 invalid. So I do some google-ing to find out why the developers of Unix or even PHP refuse to start unix epoch from, say, year 1600 ? (Windows Win32 FILETIME epoch is at January 1 1601 00:00:00 UTC, Im guessing windows is using unsigned 32-bit, because windows don't work with negative timestamps... lazy to do the calculations...) Before I got my answers, I dsicovered some interesting news.
After the Y2K problem, are you aware of the next coming bug similar to Y2K's one ?
The Y2038 problem
In computing, the year 2038 problem may cause some computer software to fail in or about the year 2038. The problem affects programs that use the POSIX time representation, which represents time as the number of seconds since January 1, 1970. This representation is standard in Unix-like operating systems and also affects software written for most other operating systems because of the broad deployment of C. On most 32-bit systems, the time_t data type used to store this second count is a signed 32-bit integer. The latest time that can be represented in this format, following the POSIX standard, is 03:14:08 UTC on January 19, 2038. Times beyond this moment will "wrap around" and be represented internally as a negative number, and cause programs to fail, since they will see these times not as being in 2038 but rather in 1970 or 1901, depending on the implementation. Erroneous calculations and decisions may therefore result.
Using a 64-bit architecture will solve this problem, delaying the date problem to about 300 billion years later. To be more precise, it will happen on Sunday, 4 December, year 292,277,026,596. After 292 billion years later, maybe a 128-bit will be used which hmm...really isn't our business anymore. Who cares what will happen after 292 billion years eh ? I don't even really care if my weblog will crash or not in year 2038... hehe... who cares anyway ?
source:
http://en.wikipedia.org/wiki/Unix_epoch
http://en.wikipedia.org/wiki/Year_2038_problem
|
|
|
|
|
