You can develop client-server applications that don't require persistent connections.
I hope you don't think that Unidata/Universe shops are going to develop 100% client-server applications that require each and every desktop to have a Unidata/Universe license. That's not the case from what I have seen. I have seen a mixture of green-screen (legacy) and client-server applications at one company. The client-server was multiplexed and that worked great. --- [EMAIL PROTECTED] wrote: > VOID isn't the right word... BTW, it was your word, > not mine. It's not > even close to being the right word. It's all out > wrong. I should have > continued quoting the next line too (below). You > didn't just imply that > it's not allowed, you said it. The very > documentation you pull out to > support your argument specifically talks about > needing license slots for > that very thing. If it's "not allowed" than there is > be no reason to > state the need for user licenses for them. > > We could even make it more interesting. Your new > argument seems to be > against the queuing of requests. I believe most > webservers queue > requests. I know for a fact that apache does. See > the docs on > MinSpareServers, MaxSpareServers, and MaxClients. > And since a webserver > is transactional and stateless (unless we consider > sessions which I'll > get into in a sec), then when does a user count and > when do they not? In > other words, I request a page from the webserver > connected to a U2 > database. I use up a user license slot. When does > that slot free back > up? When the page is done being sent? When I don't > ask for any more > pages? How you going to determine that? When my > session is over? If > sessions are used. What if they aren't? When I close > my browser? Again > how to determine that? After some arbitrary timeout? > How long and who > decides? Let's relate it to a terminal based app. > Say I want to check > inventory. I could log on, send my request, see the > answer and log out. > Is that not what the web server is doing when a page > asking for the same > this is requested and sent back? So for a terminal, > my user license is > needed from login to logout. So unless something > like sessions are being > used to maintain some type of state, then why would > the web based user > not be bound by the same rules? > > > --- D Averch wrote: > > All of the products mentioned here except RedBack > will VOID your IBM > > concurrent user license requirement. IBM does not > allow you to use > third > > party or in-house multiplexing software. > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit > http://listserver.u2ug.org/ > __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
