Neil Nelson wrote:

> But the idea in working with Marcus would be similar to working

> with the WinSCP author in that we could build up the product

> features more quickly with their software input.  We would be

> providing a background platform (IOS) on which their products

> would work, or rather we wou;ld be providing common services

> that these different products would use.  For the PIP product,

> Marcus needs a security feature.  The WinSCP product could use

> dynamic IP management and two-way-Windows security,

> WinSCP at the moment appears to be a Windows client that can

> only connect to Linux/Unix servers.

> 

> And then with you working on the text and voice communication

> products, we begin to have a suite of complementary features that

> can rival PC Anywhere and LapLink, and in some cases are

> altogether new features.

> 

> The PIP product is currently a low priority with Marcus who is

> working on his German Masters degree, but I have been trying to

> keep him interested so that when we get to a point where his

> product will easily fit into place we can press him and work

> out an arrangement.

> 

> Voice to text sounds like it might be something you are interested

> in and could work on.  Copying is easier than coding and then

> finding an author/programmer to develop a feature for our

> overall product suite would be good.  If copying, you will want

> to look carefully at the copyright/license so that you will have

> permission to make money from the copy or be able to use the

> product/feature in a way that though may not allow the product to

> be sold directly, which would be the case for the common GPL

> license, but that the product could be distributed with the others

> and then enhance the sales value overall.  A BSD, free for any use,

> or public domain copyright are best for copying.  But code can be

> redesigned from its ideas so that any code is better then no code.



... 

> However your application is in part targeted for smaller user devices that

> may not be able to efficiently use SSH because of its resource

> requirements.



I was thinking about setting a posibility to use small handy devices

that would be IOS Clients. So this is a very interesting topic. I think

a header should be used that describes weather the connection could be

encrypted or not. Simple to implent, I belive.



--



Don't feel bad about asking/telling me anything, I will always gladly

reply.



Digging for info? Try AI Meta Search:

Http://WWW.AIMetaSearch.Com



MesonAI -- If nobody else wants to do it, why shouldn't we?(TM)

Http://WWW.MesonAI.Com

