...
> Are both the Mac and the PC showing the same time?
Yes! Both computers shows the same time. The Mac is set to "CEST,
Berlin" and the Windows-Machine is set to "Daylight Time,
Berlin" (hopefully the same). Both machines are getting the actual
time from a time server.
As I recall, most versions of Windows (possibly changed in XP) store
file times in local time. These need to be converted according to
some bizarre algorithm.
The Mac - and all Unix systems - store times in GMT and convert for
display.
Craig
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
From Thu 27 Apr 2006 20:30:38 -0400
Return-Path: <realbasic-nug-bounces at lists dot realsoftware dot com>
Received: from lists.realsoftware.com (209.198.132.125) by realsoftware.com
with ESMTP (Eudora Internet Mail Server 3.1.3);
Thu, 27 Apr 2006 19:31:04 -0500
Received: from lists.realsoftware.com (localhost [127.0.0.1])
by lists.realsoftware.com (Postfix) with ESMTP
id 6702D1225FC7; Thu, 27 Apr 2006 19:30:56 -0500 (CDT)
X-Original-To: realbasic-nug at lists dot realsoftware dot com
Delivered-To: realbasic-nug at lists dot realsoftware dot com
Received: from mail1.mx.voyager.net (mail1.mx.voyager.net [216.93.66.204])
by lists.realsoftware.com (Postfix) with ESMTP id 52ACB1225FB2
for <realbasic-nug at lists dot realsoftware dot com>;
Thu, 27 Apr 2006 19:30:40 -0500 (CDT)
Received: from [192.168.0.102] (c-24-56-233-58.chrlmi.cablespeed.com
[24.56.233.58])
by mail1.mx.voyager.net (8.13.2/8.10.2) with ESMTP id k3S0UdcB005217
for <realbasic-nug at lists dot realsoftware dot com>;
Thu, 27 Apr 2006 20:30:39 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v749.3)
Content-Transfer-Encoding: 7bit
Message-Id: <028EE789-E41A-4C8C-B9DC-61AD07617F2F at kellerfarm dot com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: NUG list <realbasic-nug at lists dot realsoftware dot com>
From: andrew at kellerfarm dot com
Date: Thu, 27 Apr 2006 20:30:38 -0400
X-Mailer: Apple Mail (2.749.3)
Subject: TCP transmissions
X-BeenThere: realbasic-nug at lists dot realsoftware dot com
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Sender: realbasic-nug-bounces at lists dot realsoftware dot com
Errors-To: realbasic-nug-bounces at lists dot realsoftware dot com
I am having a bit of trouble with some TCP transmissions. Every once
in a while, a transmission is received that is not decoded properly
by my parsing subroutine. It usually works fine. I didn't think
about it very much until I noticed that sometimes, the dictionary
that is built from the transmission (my transmission parsing
subroutine returns a dictionary) is incomplete.
Is a TCP socket only supposed to fire DataAvailable when it gets a
complete transmission, or does it fire for every packet? Should I
create my own buffer and put markers at the beginning and end of the
transmission so that I know when it completes?
Thanks,
Andrew Keller
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|