Not strictly true. They can choose to remove the material and not be
liable for copyright infringement themselves, or they can ignore the
request and become liable. In reality, most will choose the first
option.
On Apr 11, 3:23 pm, Edward Falk wrote:
> My understanding is: When an ISP or other
It would be nice if some other pricing models were available (for
example, subscriptions), but I just don't see a "no returns" or even a
"no returns after 1 hour" model being very popular with users. I may
be wrong, but I don't think most people see these products as
consumables in the same way yo
You know, as a potential buyer of apps, a 24 hour return period seems
pretty reasonable, even a little short, to me. Maybe if your app can't
hold the customer's attention for that long, its not worth paying for
in the first place...
On Feb 22, 6:12 pm, JP wrote:
> On Feb 22, 1:23 pm, Java Develo
Downloading it once is probably the best approach, and also allows you
to release updates to the database that your app can check for. You
could reduce the bandwidth some by compressing it and having the app
decompress it.
On Dec 3, 1:50 pm, burton miller <[EMAIL PROTECTED]> wrote:
> i'm not tryi
The first option (Client Login API) still requires your app to get the
google userid and password from the user. The second option (OAuth/
AuthSub) only applies to web apps (although I suppose you could launch
a browser session). What would be real nice from my standpoint would
be some way to stor
5 matches
Mail list logo
