GregWhitesCarver.com

Rating: 0 - 0 votes

Company Logo

Company Name

Company Contact

Website Analysis

Domain Whois

WHOIS information for GregWhitesCarver.com

Powered by who.is

Page Type

This page is about a company.

Title

Code and Whatnot

Description

For me, on Mozilla, the current incarnation of Y!MB is working a lot faster than the first incarnation. I originally tried Beta for about an hour and decided it was just too slow to use. Now, I think I like it more than the old Yahoo! Mail. The only problem I currently see is that spell check doesn’t currently work in Mozilla. I imagine they’ll iron that out soon enough, and I love sending out typos anyway.

The most taxing operation I’ve done on the new Beta is moving every message in my Inbox (about 4000) to my Archive folder. As I was selecting all of the messages with SHIFT-PAGE DN, there were two minor problems. First, I had to press PAGE DN many times rather than holding it. Second, it (for understandable reasons) has a hard time loading all of the email headers quickly enough as I highlight downward. The drag won’t work until they’re all loaded, which is why I was using SHIFT-PAGE DN rather than holding shift and clicking on the last header. In my imagination, at least, the headers loaded faster if i went sequentially down the list. I moved about 1000 at a time - not something you can do on the old Yahoo! It’s not as snappy as a desktop app, but it’s snappier than most web apps and I have a feeling future browsers (and even future servers) will have big improvements to speed up these interactions. Another hunch I have is that Yahoo! has not thrown the big guns at this project yet, infrastructure-wise. Since AJAX responses don’t come with (much) CSS or JavaScript (or page headers, images etc.), you’d think they could be a lot faster than full page views…

COMET

My boss wanted to watch the Apache access logs from a web page. And top, and mytop. My first solution, which worked (and still works) great, was using a simple COMET stream for each feed. Keeping a process open in php means waiting for output, so I learned that it was best to have only one stream per page. I tried using iframes to display all 3 at once, but Firefox seemed to have trouble dealing with more than 2 kept-open http connections in one window. Essentially, it seemed that Firefox was waiting an arbitrary amount of time before sending out the request for the third iframe, no matter what I did.