[ZendTo] Re: Possibility of a Library

Jules Jules at Zend.To
Wed Dec 7 17:45:36 GMT 2011


I've had a good think about this overnight, and it's not looking quite 
so hard after all. My UI guy says he should be able to do it pretty 
soon, and I've worked out the overview of how to implement it.

So hopefully I'll have you something in the next few weeks.

Cheers,
Jules.

On 06/12/2011 12:56, Ortt, Richard wrote:
>
> This sounds like what we did with Pogoplug Biz (however the Biz 
> product doesn't really work).
>
> I would like to see the current single user upload to single/multiple 
> users as it is now and the static library which can be shared as 
> described.
>
> For the library portion, it would also be nice if that could map to a 
> webdav library.  That would allow users to upload files easily (even 
> map into windows file explorer), and then use an interface to share 
> the files.
>
> ________________________________________________________
>
> Message: 1
>
> Date: Tue, 6 Dec 2011 03:51:14 +0000
>
> From: Julian Adler <Julian.Adler at vectra-corp.com>
>
> Subject: [ZendTo]  Possibility of a Library
>
> To: "zendto at zend.to" <zendto at zend.to>
>
> Cc: "support at zend.to" <support at zend.to>
>
> Message-ID:
>
> <4FD0B1250A0F9846B776F975FDF14373150DD29E at VWMEC10.vectra-corp.com.au>
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Jules,
>
> I have just started setting up a Zend.to box and have it all working 
> well! Fantastic work!
>
> I was considering our requirements and one thing that we come across 
> frequently is the need to send the same file to lots of people. Not 
> necessarily at the same time like a multiple drop off. And I was 
> thinking that an admin run library of "official files" that any user 
> could create a new drop off for would be a really nifty way of 
> achieving this. A critical distinction between the multiple dropoff 
> and a library use is the different dropoff codes for each user entered 
> instead of a single code for a multiple. This would allow the tracking 
> of each request for pickup individually. The created dropoff shoudl 
> expire with the regular timeframe.
>
> For example an IT company has a pre-confiured remote support program 
> that they send to a user when they need remote help, this file is the 
> same for everyone. At the moment a new request needs to be created and 
> the file dropped off everytime. This same scenario with a library the 
> user would login, select the library and then create a new dropoff 
> with the clients email of the file from the library. The original file 
> is stored on the Zend.to box and is not subject to manipulation except 
> by administrators.
>
> Cheers
>
> Jules
>
> Regards
>
> Julian Adler
>
> Richard A. Ortt, Jr. <mailto:rortt at dnr.state.md.us> | Office 410.554.5541
>
> Engineer              | Fax 410.554.5502
>
> Coastal & Estuarine Geology
>
> MarylandGeological Survey
>
> 2300 St. Paul Street
>
> Baltimore, MD 21218
>
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://mailman.ecs.soton.ac.uk/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CITP CEng
www.Zend.To

Follow me at twitter.com/JulesFM
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654

'Teach a man to reason, and he will think for a lifetime.' - Phil Plait
'All programs have a desire to be useful' - Tron, 1982

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/zendto/attachments/20111207/483ea171/attachment.html 


More information about the ZendTo mailing list