[JDEV] Renaming

[Mike Szczerban]

I like nexus, too... if only because it sounds cool :)

Might be hard for translators, though..

Mike

On 15 May 2001 12:53:11 -0600, Michael Bauer wrote:
>  
> My $.01.  I think it should be called a nexus.  Mostly because I like that
> word and think it sounds really cool.  To a lesser degree it might even be
> more accurate.  Locus might work but I'm a Star Trek fan too.  
>  
> Seriously, never have liked resource.  Mostly because it's difficult for me
> to think of a location as a resource.  Of course, if I owned a Starbuck
> franchise or two, I might change my mind.
>  
> What about classifying things, like mike at jabber.com/device/pager
> <mailto:mike at jabber.com/device/pager>  or mike at jabber.com/location/home
> <mailto:mike at jabber.com/location/home> .  I'm an old AI hacker too.
> [Michael Bauer]   -----Original Message-----
> From: Emswiler, Mike [mailto:MEmswiler at protrader.com]
> Sent: Tuesday, May 15, 2001 11:44 AM
> To: 'jdev at jabber.org'
> Subject: RE: [JDEV] Renaming
> 
> 
> Just my $.02 worth:
>  
> It is an interesting debate.  I started working with jabber some time ago
> thinking of resource as a location, but now that I’ve used Jabber more and
> more, I tend to think of it more of a device, as in pager, cell phone, or
> even email.
>  
> For example, in my client, I find it useful to be able to send a text
> message to mikee at jabber.com/workpc <mailto:mikee at jabber.com/workpc> ,
> mikee at jabber.com/homepc <mailto:mikee at jabber.com/homepc> ,
> mikee at jabber.com/pager <mailto:mikee at jabber.com/pager> ,
> mikee at jabber.com/mobile <mailto:mikee at jabber.com/mobile>  or
> mikee at jabber.com/cell <mailto:mikee at jabber.com/cell>  , or even
> mikee at jabber.com/email <mailto:mikee at jabber.com/email>  (which just
> redirects to whatever email address I have programmed it to … during the day
> it might be my work email and at night it might be home email…)
>  
> Or I can just send to mikee at jabber.com <mailto:mikee at jabber.com>  and let my
> client determine the resource to actually deliver to based on the schedule
> and delivery mechanism I (as the end-user of my client) provide.
>  
> Of course, my client is more voice-centric and acts more like a CB than
> anything else, so mostly it goes to homepc or workpc resources … too bad
> Nextel hasn’t published a gateway to their Direct Connect feature :-) yet.
>  
> Irregardless of the client usage, *I* think resource is the perfect name
> because it is truly generic, allowing it to be a location or a device, or
> just about anything else someone might envision 10 years from now.  
>  
> However, in developing *your* client, you might find it useful to call it
> whatever you like … it’s just a display label you present to the user.
> Besides, I can’t imagine the work involved in actually renaming the thing
> throughout all the <grin> documentation, web pages, etc. or even more
> evilly, the source itself :-)
>  
> Thanks,
> MikeE