-----Original Message-----
From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] On Behalf Of
Philip Pemberton
Sent: Thursday, October 18, 2007 12:50
>James Newton wrote:
>> The main thing that I see is missing is the separation of the different
>> users. If it is going to be something that you and I and others all use
from
>> the same database, you must have separate records for my stock and your
>> stock and so on. And I don't necessarily want you to know how much of
>> something I have in stock, unless I mark the record as being public (i.e.
>> for sale)
>
>It's not really meant for multi-user applications... I built it to manage
my 
>stock. Though WebPlatform does have authentication module support, it's not

>enabled for ISIS, because it doesn't make use of it. Yet.
>
>Adding "this user owns this record" support would mostly involve query 
>tweaking. Making sure users can't edit other users' data under any 
>circumstances, and only allow public data to be viewed; only displaying the

>current user's data in the search, that sort of thing.

Err... I would like to clarify a point here... That I think is sort of
critical and that I've just realized has not actually been stated.

You are planning to add multi-user support eventually, right?

Or are you developing this for your own use only with our input?

Are you planning on releasing it as a FOSS application for individual people
to use on their own systems? This would then not require multi-user support,
but people with a web server or even a mashup of an internal web server
could then use.

Or is this something that you plan to offer as a pay service or pay
software?

I have no problem with you taking your software in any of those directions,
but I would like to know your intentions up front, before I spend anymore
time on it.

--
James

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist