• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Distributed Objects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Distributed Objects


  • Subject: Re: Distributed Objects
  • From: Daniel Beatty <email@hidden>
  • Date: Mon, 20 Mar 2006 22:24:41 -0600

Greetings Dalton,
Just looking at your code, it looks fine.   You are absolutely correct.  I should be spending some time publishing this May on some projects of mine that also use DO.   The datasets that this code works on is the Sloan Digital Sky Survey, and the FITS format that it is in can be chaotic, even with the extraordinary amount of work put in by the SDSS team.  

However, I have found that DO has numerous of benefits to those datasets and knowledge based representation as the under the hood glue between many processes attempting to perform reducts operations.   


Again I hope to publish by the end of May so that all may have the benefit of a good discussion using these DO in large multi-processor jobs.  

Later,
Dan Beatty

On Mar 3, 2006, at 6:17 AM, Dalton Hamilton wrote:

Dan,  both emails you've sent have been very helpful.  From your first email, I was then able to isolate some articles that pointed out that Cocoa archives can hold Objective-C and Java objects, scalars, arrays, structures, and strings.  Therefore, I simply changed the <protocol> of the methods to return a NSString and it I'm able to return very large NSString values from the server to the client.  

@interface Traceroute : NSObject
- (NSString *)do_trace:(NSString *)words;
@end

@implementation Traceroute
- (NSString *)do_trace:(NSString *)words {
    NSLog(@"Performing traceroute.  String = %@\n",words);

return((NSString *)@"..proper route being taken..");
}
@end

I was also able to call the do_trace and pass from the client a large string value with no problem.  

One more thing.  As you can see above, through you advice, I found that I have no problems return()'ing an NSString.  If I want to return multiple pieces of data I'm guessing that is when I need to use Marshalling/Archiving and UnArchiving.  I'd create a structure (or object) to hold the pieces of data I want to return.  I'd then send it through a Coder to Archive it then use the return() call to return the Archived value and then Unarchive it on the client side?   I haven't seen any examples of the on the net (using DO) or the books I have.  

My books do not have a good section on Marshalling/Archiving with DO -- could you give me the name of the Big Nerd book???  Also, I would very much like to see your research on NSDistantObjects.

Again, you have been very helpful, thank you.

Dalton Hamilton



Dan Beatty, M.S. CS (B.S. EECS)
Ph.D. Student 
Texas Tech University
email@hidden



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Distributed Objects (From: Dalton Hamilton <email@hidden>)
 >Re: Distributed Objects (From: email@hidden)
 >Re: Distributed Objects (From: Daniel Jalkut <email@hidden>)
 >Re: Distributed Objects (From: Dalton Hamilton <email@hidden>)

  • Prev by Date: Re: Distributed Objects
  • Next by Date: Re: Active network ports
  • Previous by thread: Re: Distributed Objects
  • Next by thread: Re: Distributed Objects
  • Index(es):
    • Date
    • Thread