I have to admit to not having read much about this (I did use webservices on a project once), but just for starters, here:
http://diveintopython.org/http_web_services/index.html http://diveintopython.org/soap_web_services/index.html Without suggesting anything too far afield, I would suggest that web2py services "naturally" serve web2py applications... We could (too) easily get into the forray of messaging services (see http://www.w3.org/2002/ws/) - but I think just looking at ground that has been covered, NOT trying to get too general (at the start - rather keeping it simple, but elegant) put following the general sense of web services could be useful. The sense of the concept I was suggesting is in this direction. Regards, Yarko On Oct 9, 12:57 pm, yarko <[EMAIL PROTECTED]> wrote: > when I said services, I was thinking from web-services model that I'm > aware of in dot-NET. > > So, my mental concept of this is such: > > a service is something that a web2py app calls like a remote procedure > call - it does the same authentication etc. of the caller, but has no > user UI interface - it's only a service > (seehttp://en.wikipedia.org/wiki/Web_service > ) > > It would, as Massimo suggested, run as a separate instance, > potentially on a separate machine - somewhere else on the network; > possibly on the same machine as Massimo showed in starting a separate > instance (an essential element of a service). > > The basic mechanics of having and calling services shouldn't be too > hard; listing and finding services would be another thing. It might > require something as simple as a standard web2py installation service > that, for proper authentication, will list (allow you to discover) > what services are offered... I'm assuming much of the basics of this > (at first) can be accomplished by simple convention. > > But when I said services, I meant web services, and specifically web > services written and served by web2py instances. > > To take Massimo's suggestion one further, rather than have one app run > it's services under a separate web2py instance, I would run a services > instance of web2py that offered a catalog of services to a select > group of clients (membership, authentication). > > Compared to a module, a module runs in the current instance of web2py > and is available to any app. A service would provide asynchronous > services, protect user response by isolating either compute or > resource or time insensitive, or times functionality to a non- > interactive instance of web2py. > > Let's keep thinking and talking about this; it's a rich topic..... > > Yarko > > On Oct 9, 8:58 am, mdipierro <[EMAIL PROTECTED]> wrote: > > > Thank you. I will look at it. > > > On Oct 9, 8:22 am, achipa <[EMAIL PROTECTED]> wrote: > > > > I think we might have a bit of a terminology issue here. From the > > > operating system's standpoint, web2py is a service. I'm not talking > > > about that. When I say web2py service, I mean things that are strictly > > > linked and (I dare say) actually are *meant* to run under web2py, but > > > are not tightly coupled with the actual actions of the user (see > > > session cleanup, cron tasks specific to the application). As a > > > requirement, web2py services should be able to run under whatever > > > platform and environment web2py is running from, something that is > > > certainly not easily achieveable if this is done as a separate > > > service. > > > > As for Steve's concern, I've just sent a proof-of-concept patch to > > > Massimo which does the above in a way that does not cause any > > > detectable performance degradation for users. > > > > As for the last post, I don't see how you can control web2py services > > > from a web2py application ? If you're not root, you have no access to > > > init scripts (and you certainly don't want web2py to run as root). If > > > you're running under mod_wsgi/fastcgi, you can't even control the > > > current running process, much less influence the actual webserver > > > web2py is behind. > > > > On Oct 9, 8:04 am, mdipierro <[EMAIL PROTECTED]> wrote: > > > > > Anyway.... it would be possibl, and I do not see anything wrong with, > > > > creating a web2py app that provide an OS interface to start and stop > > > > web2py services. > > > > Anybody? > > > > > Massimo > > > > > On Oct 9, 12:41 am, mdipierro <[EMAIL PROTECTED]> wrote: > > > > > > I agree with Steve. Running services from inside web2py is not clean. > > > > > Consider that web2py threads are managed by the web server and are > > > > > subject to many limitations because of security (timeout, limited > > > > > permissions, etc.). Services instead are supposed to be managed by the > > > > > os and may need to run without timeout and with less restrictive > > > > > permissions. > > > > > > Notice that you can create a folder "services" under you app and then > > > > > start another instance of web2py from the shell using > > > > > > nohup python web2py.py -S yourapp -M -R applications/yourapp/services/ > > > > > yourservice.py & > > > > > > On Oct 8, 8:57 pm, "Steve Shepherd" <[EMAIL PROTECTED]> wrote: > > > > > > > Is this as a response to remoinvg the usage of CRON? > > > > > > Does the overhead hurt Web2py performance? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
