We have lots of clients who haven’t moved away from VC 6 yet. At present we need to maintain all our projects in a VC 6 compilable form. The easiest way to do this is just to use VC 6 as our primary development platform for C++. If we had a tool that allowed us to back port VS.Net 2003 projects to VC 6 then we could maintain the projects in the latest format and back port as required.
I ran Outlook against my POP3 server just now and once again was unimpressed by the speed that messages were being downloaded. It seems that Outlook 2002, over an SSL link to a POP3 server (so no anti-virus weirdness is going on) takes about half a second per message to download a large number of really small messages, from a server on the same machine…
Because I’m curious, and because it doesn’t appear to be a server issue as the server idles the whole time, I ran up Outlook Express and pointed that at the server (same SSL connection), it flew.
<rant>Whoever decided that it would be a good idea for the explorer status bar to be ‘switch offable by someone other than the user’ should be taken outside and given a good kicking. Why is it a good to let someone other than the user decide what’s the best way to display information?</rant>
and don’t get me started on folder views that reset themselves to the dumb ass icon display for no apparant reason…
I’m making the compiled version of our Bluetooth server shell available for download here. The source is not available at this time.
The zip contains a simple server that advertises the following Bluetooth profiles: OBEX file transfer, Serial Port, Dial up Networking, LAN Access Server and OBEX object push.
The server requires working Bluetooth hardware that uses the XP SP1 stack. If you don’t know what this means then chances are, you don’t have it.
37 today.
So there I was, cleaning my teeth, about to get into bed and suddenly I saw a reason for using AcceptEx… I’ve known about AcceptEx for ages, and even written an article about how to use it but I always thought that it just wasn’t something I needed to use in our servers. I’d latched on to the officially advertised reasons for using it and ignored the more subtle advantages…
Er, I blame him, him and hiiim, oh and that little voice inside my head…
We’re developing some code for a client. There’s a standalone server, which we’ve completed, and a small stub of code that allows the client’s existing system to talk to our new server in place of the old thing they used to talk to…
This morning I stubbed out the new stub and put together a test harness project. Unfortunately, due to the way the client’s code is coupled it could prove difficult to test the new stub…
Earlier I said “I’ll probably keep the code for now, but it’s not the code I’d have written first if I was working from a test. I wouldn’t need it yet… I may never need it in production…” I lied. It’s in CVS if I need it, so why keep it cluttering up the code when I don’t need it…
Way back in June I was playing around with OBEX. I’ve had a quiet day today and went back to the code to progress it a little more (a client is making interested noises so I need to get back up to speed again). The code I wrote in June was before I’d become test infected…
The first thing to do, of course, was to add a test harness and a mock object library to the OBEX library.
