Return-Path: william@bourbon.usc.edu Delivery-Date: Mon Sep 8 20:13:31 2008 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.3 Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75]) by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id m893DVqj030443 for ; Mon, 8 Sep 2008 20:13:31 -0700 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m893Cc5e013273 for ; Mon, 8 Sep 2008 20:12:38 -0700 Message-Id: <200809090312.m893Cc5e013273@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Regarding data being sent Date: Mon, 08 Sep 2008 20:12:38 -0700 From: Bill Cheng Someone wrote: > Is it enough if the request/response strings alone are ascii or even the > processing within the server/client should also have non ascii string? Ex: > after receiving the string on the server can I add a null character to the > end of the string ? What data structure you use for your server and client are intentionally not specified. So, you use what you want, as long as it works. -- Bill Cheng // bill.cheng@usc.edu